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

Allow decimal values for "break time divisor" #63

Closed
CactiChameleon9 opened this issue Jun 22, 2023 · 3 comments · Fixed by #78
Closed

Allow decimal values for "break time divisor" #63

CactiChameleon9 opened this issue Jun 22, 2023 · 3 comments · Fixed by #78

Comments

@CactiChameleon9
Copy link

While dividing works well for controlling how much break you get per work, it currently lacks a lot of granularity.

Current values allow for: 50%, 33%, 25%, 20%, 17%, 14%, 12.5%, 11%, 10%

Say I wanted something like 40%, or a 3 divisor felt too long but 4 too short?

I therefore propose that you allow users to enter any decimal value in the text field, but keep the (+) and (-) buttons so it is user friendly

@Diego-Ivan
Copy link
Owner

I've been thinking about this feature and I think the percentages might work better than decimal divisors. A preference that allows the user to choose Percentage of work time to take a break sounds good to me. Limiting the values from 10% to 50% seems reasonable as well. What do you think?

@CactiChameleon9
Copy link
Author

CactiChameleon9 commented Oct 15, 2023

I think that would be more user friendly. I think people would have a better understanding of a percentage-based system

Can I suggest allowing a manual override of limits?
I like having +/- butttons (that say adjust by 5% in your 50%-10% range), but it would be useful to be able to manually type in 200% if, for example, I wanted to get a small amount of work done for a more chilled day.

@Diego-Ivan Diego-Ivan linked a pull request Oct 15, 2023 that will close this issue
@Diego-Ivan
Copy link
Owner

Can I suggest allowing a manual override of limits? I like having +/- butttons (that say adjust by 5% in your 50%-10% range), but it would be useful to be able to manually type in 200% if, for example, I wanted to get a small amount of work done for a more chilled day.

Changing limits is a little bit more complicated. I limited it to 100%, it is more permissive than the 50% maximum I first thought of. Still, I believe going over that limit is somewhat against the principles of the Flowtime method, which is using it for tasks you enjoy doing. I do not want to limit the user's freedom more than that, and I doubt many users will decide to go over the 50% point anyways, the default and only possible value was 25% for quite a long time, which is the original time fraction for the Flowtime technique.

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

Successfully merging a pull request may close this issue.

2 participants