On 06 Sep 2002 12:56:39 +0100, John Latham wrote: > > This has also made me realise something, perhaps worth suggesting. It appears > that the window buttons are activated either on press or release, depending on > what they are bound to. It seems they are activated on release if they are > bound to a builtin, and on press if they are bound to a Menu or Function. I > can see why some would argue it is good for them to activate on press if they > are bound to a menu. But I'm not sure this behaviour is the right one for a > function. > > Generally I would say that activation on release should be the default for all > buttons, in any GUI, so that if the user has pressed the wrong button, s/he > can move the mouse away before releasing, to avoid the activation. Any > exception to this should be for convenience and only for something which is > safe, e.g. a Menu that has no default operation. > > I have just changed my maximize buttons so that they invoke a function to do > an animated maximize, using FvwmAnimate instead of a simple Maximize X Y. Now > they activate on press instead of release! > > Perhaps, ultimately, the window buttons could be given a ButtonStyle option so > the user can decide which is most appropriate? Or is there already some way to > control this?
Just always bind a complex function, then you have a lot of options. "I" to execute a command on press, "C" or "D" - on release (but there are some issues), "M" and "H" change the "feel" as well. Try to omit or add "C", "M", "H" to get different combinations of "feel". Regards, Mikhael. -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
