Bug 2228 - No option for entry initially highlighted upon opening a menu
Status: CLOSED FIXED
Alias: None
Product: Openbox
Classification: Unclassified
Component: general
Version: 3.3
Hardware: PC Linux
: P2 minor
Assignee: Mikachu
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2005-03-29 14:17 EST by James Michael Fultz
Modified: 2007-05-16 15:52:38 EDT
1 user (show)

See Also:



Description James Michael Fultz 2005-03-29 14:17:18 EST
Since Openbox 3.3-rc1, there is no menu entry initially highlighted upon opening
a menu. Openbox 3.2 and prior versions would highlight the first menu entry upon
opening a menu.  The behavior of Openbox 3.2 in this regard saves time when
opening a menu via keybinding:  fewer keystrokes are necessary to access the
desired entry, especially if it is the first entry.  Matter-of-fact, I cannot
think of any instance where this behavior would be undesirable.

There was a hilightFirst configuration option with Openbox 3.2, but it did not
effect this behavior.  When the option was removed, the menu entry highlighting
behavior was also changed to what it is now.  Unfortunately, I had not rtested
this until now and find that I prefer the old behavior.
Comment 1 Jeremy Nickurak 2005-05-19 01:45:12 EDT
It's undesirable if your menu configuration puts a large series of nested
submenus under the first entry. If this is the debian menu for example, this
behavior instantly results in 4 menus being opened on my selection of
applications. given how large they are, this often means that the menu gets
pushed off to another location to make room for all the submenus. Similar
problems show up if the desktops menu is the first entry.

Of course, with the menu moving around, the cursor jumps over quite a bit too.
So I'll highlight a menu entry when I'm good and ready :)

I do see the value of it in a keyboard binding though. Perhaps a
"highlightFirst" option on the show-menu action would be useful. Then it could
apply strictly to those cases where the keyboard has triggered the action, or
simply whenever the user wanted it, without cluttering the main code with a root
preference.
Comment 2 Mikachu 2006-04-20 14:43:08 EDT
I just reverted the behaviour but i'll leave this bug open because of the option suggestion.
Comment 3 Mikachu 2006-08-02 09:57:01 EDT
I have made it so the entry is only hilighted if it is a normal entry, ie not a submenu.