Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Percentages should be derived #19

Open
arbadacarbaYK opened this issue Apr 25, 2024 · 0 comments
Open

[Feature Request] Percentages should be derived #19

arbadacarbaYK opened this issue Apr 25, 2024 · 0 comments

Comments

@arbadacarbaYK
Copy link
Contributor

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 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant