Hi,

When I have a rest break and block mode is at "block input", most of the input is indeed blocked but not all!!
I can't do anything anymore with windows related programs, but I still can continue working in my Linux environment that runs in Exceed onDemand (v 13.7.8)
Mouse nor keyboard input is blocked.

This is opposite to what is supposed to happen of course, as Workrave is used in this way as a self-protection to the user. So I gave it severity "major" (not higher since it isn't completely blocking Workrave from working).

Regards,
Walter.

Workrave 1.9.4 does not block 64 bit application. The next version will.

Please try a recent snapshot and check if this version fixes your problem, e.g.:

http://snapshots.workrave.org/20111022/workrave-win32-v1_9_900-4-g20b4efeafa-20111022-installer.exe

Thanks.

Hi Rob,

Downloaded and installed the snapshot (compact installation) and that indeed blocks Exceed onDemand as well. Now you mention it... you're right, it's a 64-bit application.

In attempt to see whether there still might be a way around the blockage I have tried several things. Only thing that seems to be possible is using a bindkey combination to open a menu of the Linux window-under-focus (LeftAlt + underlined_menu_character), as a matter of fact: *all* LeftAlt + <key> bindkeys gave response, but after that I haven't been able to do more (yet).
So I couldn't give the opened menu a follow up by e.g. mouse-clicking / using arrow keys / typing underlined_menu-item_character. Also using a direct bindkey combination like Ctrl + N didn't give me a way to undermine the blockage.

As for me, this ticket could be put to Resolved & Fixed, unless you want to dive into also blocking the LeftAlt + <key> combination.

Regards,
Walter.

Forgot to thank you for solving... so here you go: cheers!

I noticed some other improvement that goes along with this version: it's now not possible anymore during a Break to right click the systray icon and change mode to Suspended or Quiet.
I have the Postpone button disabled and sometimes I used above method to circumvent the break, which of course was not correct that it was possible.

Now one cannot go around the break like that anymore as well! ;-)