Bugzilla – Bug 4436Cycling windows with mouse wheel up/down (in Desktop context) requires pressing ENTER to *activate* window and locks out keyboad input.Last modified: 2010-04-29 16:19:05 EDT
This is a read-only, static archive of bugzilla.icculus.org
Bug 4436
- Cycling windows with mouse wheel up/down (in Desktop context) requires pressing ENTER to *activate* window and locks out keyboad input.
Openbox 3.4.9 on Arch Linux (rolling distro, all up-to-date packages).
This functionality was OK in previous Openbox version.
Symptoms: using mouse wheel up/down windows cycle OK, window focus gets set but window can't be activated with the mouse and MUST be activated by pressing ENTER/RETURN on the keyboard.
The relevant section of the config file: ~/.config/openbox/rc.xml
<context name="Desktop">
<mousebind button="Up" action="Click">
<action name="PreviousWindow">
<dialog>no</dialog>
<bar>yes</bar>
<raise>yes</raise>
<linear>no</linear>
</action>
</mousebind>
<mousebind button="Down" action="Click">
<action name="NextWindow">
<dialog>no</dialog>
<bar>yes</bar>
<raise>yes</raise>
<linear>no</linear>
</action>
</mousebind>
</context>
The same behaviour is observed with action="Press".
In previous versions, focus was not allowed to be moved while an interactive action (window cycling) was taking place. Now it is allowed, so focus is moved and the window cycling is left uninterrupted, allowing you do move focus and continue cycling.
I've made the Focus action stop all interactive actions by default, and added a stopInteractive option which can be set to false, allowing you to focus things without interrupting focus cycling, if that's what one would like to do.
I might change how this is handled in future versions again.. but always providing a way to keep this behaviour as you have been using it.
I really appreciate your explanation of this new version behaviour and at the same time I apologize for filing a report for a bug which wasn't a bug at all.
In my defence, I could not find any documentation with the above info. In fact, I still can't find anything on that new 'stopInteractive' option. I've tried adding <stopInteractive>no</stopInteractive> in the <focus> section as well as the <context> section mentioned in my original post. I've tried setting the option to 'no', 'false', 'yes', etc. to no avail.
I know this isn't the support area but could you please point me to where I should look to get more info on how to set it up the way windows cycling used to work?
Moreover, I noticed that if I currently bind (for example) 'W-Up' instead of just 'Up', then everything works as it did in the previous version. Strange.
When Dana says "I've added", she means she did it right then, so it's not released yet. You'll have to wait a bit :).
The reason W-Up works is because openbox can notice you let go of W, but if you have just Up, there's nothing to say you're done.
I've been looking forward to seeing this functionality but I don't believe it's been implemented yet. What's the status on this?
The current behaviour with 3.4.11.1 is still to cycle through windows *unfocused* requiring a mouse click or ENTER on keyboard to activate/focus window.
What about the 'stopInteractive' config option?
Thanks.
OK, unfocused is not the correct word to describe it. Basically, the window would gain focus but have the "selection frame" around it - is what I meant.
Thanks again.
(In reply to comment #5)
> I've been looking forward to seeing this functionality but I don't believe it's
> been implemented yet. What's the status on this?
It's in my git tree for the 3.5 branch. It included some pretty significant changes in the action code so I didn't backport it to 3.4.
I was hoping to start pushing out some 3.5 betas soon but got very busy so it's taken some time.
> The current behaviour with 3.4.11.1 is still to cycle through windows
> *unfocused* requiring a mouse click or ENTER on keyboard to activate/focus
> window.
>
> What about the 'stopInteractive' config option?
The stopInteractive option allows 3.5/git-version to behave the way 3.4 currently does. By default it will work the way you are looking for.
Openbox 3.4.9 on Arch Linux (rolling distro, all up-to-date packages). This functionality was OK in previous Openbox version. Symptoms: using mouse wheel up/down windows cycle OK, window focus gets set but window can't be activated with the mouse and MUST be activated by pressing ENTER/RETURN on the keyboard. The relevant section of the config file: ~/.config/openbox/rc.xml <context name="Desktop"> <mousebind button="Up" action="Click"> <action name="PreviousWindow"> <dialog>no</dialog> <bar>yes</bar> <raise>yes</raise> <linear>no</linear> </action> </mousebind> <mousebind button="Down" action="Click"> <action name="NextWindow"> <dialog>no</dialog> <bar>yes</bar> <raise>yes</raise> <linear>no</linear> </action> </mousebind> </context> The same behaviour is observed with action="Press".