Re: Handling rests

Dieter Egert <[email protected]> writes:

> Hello
>
> I'm using workrave for some years, now with the newest version 1.9.1.
> It's a great tool.
>
> But I'm missing an improvement in this situations:
>
> Let's say I have a rest, come back to the pc and continue working.
> Then sometimes I get a workrave message to have a micropause or a
> normal break. The timer was stopped while my rest, but not resetted.
> Therefore when I came back it continued to count further at the point
> before my break. That is a bit annoying to me.
>
> Better would be: If I have a rest the timers (micropause and usual
> pause) of workrave not only stops counting, but (after some time) it
> will be resetted to 0. So when I continue working all timers will
> start counting again with 0.

As far as I know, this is what already happens.  So it might be a bug
that this is not working for you.  What should happen is that when you
go idle, Workrave will start counting your idle time and when it
reaches that duration that a break would be, the timer for that break
will be reset.

> Also it would be great, if it is possible to define regular rests in
> workrave. This means for example I define a rest starting each day at
> 12:00 until 12:30, and another regular rest from 09:00 until 09:15. In
> this way I don't miss these rests while I'm working.

You might want to see some of my earlier messages to this mailing
list.  I use cron jobs to run gconftool to change Workrave's settings
at specific times of day.  There is no facility for this within
Workrave itself, but (except where there are bugs) it is scriptable.

> Third improvement: The buttons to ignore a workrave pause could be a
> bit hidden. The buttons will not appear in the popup window but only
> in the context menu of workrave in the system tray. So you have to
> search them, and no longer you can click it away without thinking
> about.

This is a good suggestion.

Here are some additional suggestions regarding the “skip” and
“postpone” buttons:

1. It should be possible to disable the “skip” button for a particular
   break while keeping the “postpone” button.  Right now, in the
   preferences you either have to choose for each kind of break to
   have both buttons, or neither button.

2. It should be possible to make the “skip” and “postpone” buttons
   progressively more difficult to use.  This could be done by having
   them launch a program which the user must interact with, or which
   could play some loud and very obnoxious noise.  Sometimes, it is
   necessary to keep the option to postpone a break, but desirable to
   discourage it.

I hope this message is helpful.

-- 
With my best regards,

Joe


------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
Workrave-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/workrave-user