Re: FVWM: Invoking a menu for a window through a function

From: Marcus Lundblad <ml_at_update.uu.se>
Date: Wed, 1 Jan 2003 14:13:19 +0100 (CET)

> You probably use MouseFocus. With SloppyFocus you would not see
> "nothing happens".

Actually, when using ClickToFocus and Lenience, the FVWM tear-off menus
takes focus (when clicked).
Also

Next (HasPointer, HasHandles)
worked for xclock but not the tear-offs


>
> Current works on the currently focused window, not on the pressed window.
> All decoration/window based bindings are executed in the window context,
> to use it there is ThisWindow conditional.
>
> ThisWindow (HasHandles) Menu Window-Menu Interior 0 0 Close

I changed to ThisWindow and it does what I had in mind.
Thanks.

Actually I have some vague plans for enhancing the syntax for menu
definitions to allow for example exclusion of items for windows matching
certain conditions. This would would eliminate the need for a hack like
this, having several similar definitions.

//Marcus

--
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 majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Wed Jan 01 2003 - 07:15:04 GMT

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:54 BST