> When a menu is activated, no buttons may be pressed/depressed. > So a menu button should be depressed either before a menu started or > after it is closed. > > > selecting an entry in the menu it's operation are not directly applied to > > the window in question, instead the pointer changes to a crosshair to > > select a window for the operation > > > (This is using 2.5.1) > > I would suggest: > > Mouse 1 1 A Schedule 0 WindowId $w Menu WindowOps Delete > > but this only makes Delete work, not a menu. > I think you can't run an arbitrary menu in a window context. > > So currently what you want seems impossible to me. The behaviour where the > menu button is pressed on a menu popup is not bad, you may get used to it. > Also some people may like Popup instead of Menu (don't add Delete here): >
I tried using a function with different actions for click, hold and double-click with som variations using Schedule, but I didn't get it to work that way. So I guess it's not possible. > Mouse 1 1 A Popup WindowOps > > 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] > -- 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]
