On Tue, 26 Nov 2013 10:35:55 +0100 Vincent Lefevre <vinc...@vinc17.net> wrote: > On 2013-11-26 00:12:09 -0800, Vincent W. Chen wrote: > > On Sat, Oct 26, 2013 at 4:50 PM, Vincent Lefevre <vinc...@vinc17.net> wrote: > > > On 2013-10-25 17:42:54 -0700, Vincent W. Chen wrote: > > >> > No, "Mouse 4" and "Mouse 5" would still be allowed, but "Mouse 0" > > >> > should > > >> > be equivalent to "Mouse 1 or 2 or 3". This makes more sense. > > >> > > > > > Currently the man page is still buggy. Or perhaps the intent of > > > "Mouse 0" is not to include the scroll up & down events (just like > > > with mouse navigation in menus). > > > > > Would it be sufficient if the manpage is changed to read "Pressing any > > mouse button (other than buttons 4 and 5) while a menu is open ..."? > > The manpage should be changed. But I also think that there should be > a warning to say that "Mouse 0" will also include mouse wheel events > in practice and that a user who don't want such events to be take > into account mustn't use "Mouse 0". >
I have looked into this a little bit and don't think there is an inconsistency. The issue I see is there are default bindings for menus configured in /usr/share/fvwm/ConfigFvwmDefaults. The four lines of interest are Mouse 0 MI A MenuSelectItem Mouse 0 MTS A MenuLeaveSubmenu Silent Mouse 4 MIT A MenuScroll -1 Silent Mouse 5 MIT A MenuScroll +1 This first defines all mouse buttons via "Mouse 0" do something, then defines additional bindings to buttons 4 and 5. So it isn't that fvwm is treating bindings in Menus differently, but the defaults are configured so the mouse 4 and 5 on a menu act differently than the other mouse buttons. I was able to remove the two Mouse 4 and Mouse 5 bindings above and then redefine the Mouse 0 bindings in the menu and was able to trigger menu items from the scroll wheel. I don't see this as a bug, but working as designed. I have also found in the manpage under Mouse Navigation talking about how the mouse wheel is configured to scroll by default. Additionally I have found under the Mouse description in the manpage that "If Button is zero then any button performs the specified function." So the manpage is correctly describing the behavior. Additionally this means any not just buttons 1-5, it is just those are the only buttons fully supported. This could also cause the option to be triggered for buttons > 5, it is just >5 buttons are not always fully supported for all things in X. Does this resolve the issue, or do you still think the manpage needs to be more clear on this behavior? I do agree that having to write multiple lines to get what you need configured is not ideal, but current fvwm config syntax won't allow it and fvwm2 development is mostly ended so we have to use the config options in its current state. jaimos
