The title says it all, I dont know if this is ever possible. I have tried to just call the module, but even if the main fvwmbuttons bar panelized it before, it is opened again (as a new instance) if i just bind it this way:
Key F2 A M FvwmButtons FvwmLauncherPanel
I dont know how to do this and I doubt it is even possible, cause of this:
Action [(options)] command
Specifies an fvwm command to be executed when the button
is activated by pressing return or a mouse button. The
command needs to be quoted if it contains a comma or a
closing parenthesis.
The current options of the Action are: Mouse n -
I suppose that I could always emulate the thing by using another fvwmbuttons panel and AnimatedMove and binding it to a key, what do you think?
Are you trying to show/hide a panel from a keystroke? I’m not sure I’m understanding you correctly. If you are, I do that in my config, although I swallow things inside of the panel and show/hide those. These are the relevant bits of my fvwm config:
Umh! Interesting, really interesting. Yes, this is what I was looking for. I like overall the way you save the current cursor position to restore it later. Really a clean solution.
Well, the only downside is that the button is not the only element in the panel, so I will have to:
1.- Play with WartToWIndows X,Y values, or
2.- Create a lonely panel just to hold that button
Anyway thanks so much, as always, amazed by the fvwm way to do things 8) -Regards
EDIT: I choosed to play with the wartowindow values, since I have three panelized panels into the main one, parametrised the offset and got this:
Yep, fakeclick is sort of a hack. I’ve been using it for years though with no problem. You are also correct that it doesn’t handle if I move my panel without me also updating the fakeclick coords. I have my panels hug the upper right and lower right corners so they don’t move.
~telengard
[edit] just realized that it jumps to the window and clicks and I didn’t have to specify the coords. Been so long since I got that working I forgot how it works.
Well, the positions are relative to the base panel window, so it shouldnt matter if you move that window around (anyway this panel is fixed thru Style), while the button stays in the same relative position of the panel (in this case 50 85, for example), am I wrong? The only annoying thing that I can notice is a flickering in the mouse pointer (natural I think).
Of course, the real solution would be to implement into fvwm a native way to comunicate with these buttons via bindings, but for now there is no such option…