On Sat, Jun 29, 2002 at 11:21:52AM +0000, Mikhael Goikhman wrote:
> Currently it seems impossible to invoke an arbitrary menu in a window
> context. I.e. the following does not work as expected:
>
> Next (MyWindow) Menu WindowOperations
>
> The only way to set a window context is using a module protocol, like:
>
> SendToModule FvwmPerl eval $module->send("Menu WindowOperations", 0x3e0000e)
>
> Is there a reason for this?
No, I don't think this was intended. It was caused by one of
these evil global variables. Although every command gets the
window context passed in via the "context" variable, there was
still a global named "Context". It was basically a write only
variable that was used in the menu_func() by accident (instead of
using the correct value from "context"). I have cleaned up this
mess and removed that global. Please double check if the context
from modules still works.
> Also, what does is_menu_from_frame_or_window_or_titlebar mean?
> It is set to False 6 times and to True one time, but not used.
Looks like some unfinished work to get a window context for tear
off menus. I have removed it since I don't understand it anymore.
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
