GNOME Bugzilla – Bug 123120
RFE: sub-minute breaks
Last modified: 2006-08-19 19:18:54 UTC
The current preferences dialog allows the user to specify how many minutes a break should last. I'd like the ability to specify a period that is less than a minute. The reason for this is I want to use DrWright to rest my eyes, rather than my hands. The eye doctor suggests resting my eyes every 20 minutes for 20 seconds.
Moving to control-center: search for "Andrew doing reassignment work" to get rid of this spam e-mail.
Created attachment 29442 [details] [review] Initial patch with problem This patch set two keys for the break time: break_time_minutes and break_time_seconds. In the typing break calculates according this two keys. But I have the problem that the keys are creates as floats instead of int and I don't see how create it as int. Any hints ? The glade changes also it's include in the patch.
Created attachment 29564 [details] [review] Proposed patch. This patch update the glade file to current cvs.
Created attachment 29565 [details] [review] Patch agains libgnome schemes This patch adds a key (break_time_seconds) and rename another (break_time to break_time_minutes) necesary to fix the bug.
Added the patch keyword
The problem is that we can't rename schemas or change their meaning. Once they're used we need to continue supporting them, otherwise things will break when upgrading.
So, can we continue using the break_time key for minutes as today and add the break_time_seconds ?
I think it clutters the UI a bit too much to add a second spinbutton... could it work to just have it accept floats instead? It's not like you need to add an exact value like 1 minutes 27 seconds, but rather something like 1.5 minutes.
But, as in the case that the original reporter, if the user wants stops for 20 seconds, he must calculate the fraction (0.33 in this case) which I think have more usuability issues.
Well, in my opinion, the typing monitor isn't a tool of that kind where you can very specifically tweak the behavior. There are other tools (like workrave) that are a lot more advanced in those terms.
I think this feature it's useful, not it's an advanced feature. Workrave it's for advanced use. Well, I think we need to decide what to todo with the bug, WONTFIX or going with it?
I'll try the patch and see how it feels. If it doesn't clutter the UI too much maybe it's ok. Otherwise we can try my suggestion with a float entry. It's not like we need to say yes or no right now, 2.10 is 6 months away...
*** Bug 127419 has been marked as a duplicate of this bug. ***
I will go ahead and close this as WONTFIX. The reasons are stated above, float entry is a bit awkward and an extra spinbutton for seconds it just not worth it imo. Workrave should be used for more control/a real RSI prevention tool.