Bug 971 - Submenu often closes before I have time to click in it.
Status:
NEW
Component:
GUI
Version:
1.9.3
Hardware:
PC Windows 7
Importance:
P3 normal
Target Milestone:
---
Assignee:
Rob Caelers
URL:
Depends on:
Blocks:
Reported:
Jan 21 2011 13:47:39 UTC
by:
Walter
Modified:
Jul 8 2011 09:24:10 UTC
WhoWhenWhatRemovedAdded
Description
Walter  Jan 21 2011 13:47:39 UTC
Hi,

When I click on the systray icon with RMB to open the menu, then move the mouse cursor to e.g. item "Mode" or "Network" a submenu opens with the applicable choices for that item.
Now when moving the mouse cursor into that submenu, the whole menu tree disappears very quickly, before I can click the option of my choice!

Hence putting Workrave in Quiet or Suspended mode (as I sometimes need to) is quite an impossible job to do via mouse...

A work around (rather annoying) seems to be:
* RMB on the systray icon (main menu opens)
* LMB on Open (Status Window opens, Workrave gets the focus)
* RMB on the systray icon again (main menu opens)
* LMB on Mode (submenu -that was auto-opened due to hovering over Mode- closes)
* Right Arrow key (submenu opens again, item "Normal" is selected)
* Up/Down Arrow keys to select item + Enter to activate it

Some details that can be of interest for you when reproducing/debugging:
- In my situation the submenu opens to the left of the main menu, as the main menu is too close to the screen edge to fit the submenu in between.
- My Windows Taskbar is set to Auto Hide. But note: when the menu tree disappears, the Taskbar does NOT return to hidden state, it stays high until I click in an other program to continue work.

Kind regards,
Walter.
Comment 1
Walter  Jul 8 2011 09:24:10 UTC
Hi,

I'm now running Workrave v1.9.4 and my OS changed to Windows 7 Enterprise (64
bit) with Service Pack 1.
The submenus of which I told that they disappeared before I could click in it, now stay open!
So if you changed it in the program: it is now tested to be o.k. hence ticket can be closed.
If you didn't change anything in the program: then it is probably a problem present in Windows-XP (and maybe other OS's).

Regards,
Walter.