Thomas Adam writes: > > > > Way cool dudeski, thanks! > > What about now with the attached patch? >
Yep. Checked both settings of the option, and the behavior seems to toggle appropriately. Thanks again for your responsiveness on this. This option now allows even more mimic-compatibility with my old favorite WM, olvwm. :) I have a minor beef with the way it's documented though. I'll send a suggested wording change diff later this evening, but have to run out for a few hours now. Btw, there's a subtle side-effect of the new mode; not a problem at all, just something to be aware of: In the original (now default) mode, if a hotkey is uniquely associated with a submenu entry, then as soon as that hotkey is pressed, the submenu pops and the pointer warps to the top entry of the invoked submenu. Thus, since the pointer has warped to the submenu, subsequent hotkey presses "automatically" apply to the submenu, so to speak. In the new mode (i.e. !HotKeyActivates...) the submenu pops, but the pointer remains over the original menu entry (and sensibly so, since in the new mode, the item hasn't yet been invoked) and thus subsequent hotkey presses apply to the original menu, not to the just-popped submenu. I'm not implying there's anything wrong with this; just pointing it out, because it confused me a little when I was testing it and toggling back and forth between the two modes. It's entirely consistent with the change in selection semantics for the subcase of a uniquely associated hotkey.
