Description
When defining big splits that are constantly changing in targets its a pain to set the % for each whenever someone joined or left..
Given the amount to split is always 100% :
Every % which is not set by the user (before saving all targets) should be derived by amount of targets.
On adding/deletion of target only fields that have been derived since it was last saved need to change.
Overwriting overrules automation for that field (until saving).
Pretty sure you get the idea, anyhow..
scenario A
Target A - left empty/derived 33.33
Target B - left empty/derived 33.33
Target C- left empty/derived 33.33
-- SAVING
scenario B
Target A - user input 40
Target B - left empty/derived 30
Target C- left empty/derived 30
-> Then user overrides C
Target A - stays 40
Target B - derived 20
Target C- user input 40
-- SAVING
If user saves targets before overwriting, the Target A would also change in this example - which is fine to be redone imo, its more usual that all get the same, right ?