In user gui it is possible to check "block user input" and "block user input and screen", I think that it will be good when there will be "block screen only". Now it is not possible to do it.

(In reply to jankoweb from comment #0)
> In user gui it is possible to check "block user input" and "block user input
> and screen", I think that it will be good when there will be "block screen
> only". Now it is not possible to do it.

I am confused
* "block user input" means that any keyboard or mouse usage will be ignored
* "block screen" means that you will be shown a black screen or a screensaver or so. I.e. you will not be able to see what you were doing.

I can see the point of "block user input and screen" (i.e. ignore keyboard and mouse, and show me a black screen", but I don't understand what would be the point of "block screen but not input", as you request. You'd be able to continue working, but not see what you are doing. Roughly the equivalent of using the computer blindfolded.

Surely, that cannot be what you ask. Could you please clarify?

Sorry for confusing. I formulated it in bad way:-)

Explanation: now I have checked "block user input and screen" and when I move with mouse (e.g. I only push my table), workrave blocking window starts to flash and timer is paused for some time.

Main point of my suggestion is to be able move with my mouse without disturbing timer - so: block screen and ignore mouse and keyboard.

(In reply to jankoweb from comment #2)

I see. Thanks for the clarification. Why would you want to do that? You would just be fidgeting with mouse and keyboard without doing anything useful, right?

To avoid pausing (In reply to Kees-Jan Dijkzeul from comment #3)
> (In reply to jankoweb from comment #2)
> 
> I see. Thanks for the clarification. Why would you want to do that? You
> would just be fidgeting with mouse and keyboard without doing anything
> useful, right?

Yes:) To be able to avoid unwanted stopping of timer by random movement like fidgeting with table or when I hit my mouse with a notepad (on pause I often write down some notes on paper notepad). It is very disturbing mainly for micropause when I have my hand on the mouse or I harry - it makes me angry;)

(In reply to jankoweb from comment #4)

I'm sorry I have to keep asking more questions

- Short movements (less than a second), like bumping the mouse with a notepad, should not cause the timer to pause, even if the movement is large. This is built in the way the activity monitor works. It was originally called "cleaning lady protection", but I guess it works for notepads too ;-)

- Small but continuous movement can be ignored with the latest workrave snapshot. You can set the amount of pixels to ignore. Some mouses trigger small movements regardless of usage. Also, for me sometimes the floor shakes, causing mouse movements. All of these can be ignored.

- During micropause, you really should let go of your mouse, otherwise your muscles won't relax. If you don't let go of the mouse, you might as well not have a micropause, and solve your problem that way ;-)

Does this help?

(In reply to Kees-Jan Dijkzeul from comment #5)
> (In reply to jankoweb from comment #4)
> 
> I'm sorry I have to keep asking more questions
> 
> - Short movements (less than a second), like bumping the mouse with a
> notepad, should not cause the timer to pause, even if the movement is large.
> This is built in the way the activity monitor works. It was originally
> called "cleaning lady protection", but I guess it works for notepads too ;-)
> 
> - Small but continuous movement can be ignored with the latest workrave
> snapshot. You can set the amount of pixels to ignore. Some mouses trigger
> small movements regardless of usage. Also, for me sometimes the floor
> shakes, causing mouse movements. All of these can be ignored.
It is strange - in my case only moving my hand off the mouse cause timer stopping. :( (linux version 1.10.1) Is it possible to set it somewhere in config?
 
> - During micropause, you really should let go of your mouse, otherwise your
> muscles won't relax. If you don't let go of the mouse, you might as well not
> have a micropause, and solve your problem that way ;-)
You are right:-DDD