Re: Please Help on Customizing Start-Menu
Hi Dominik ?? 2004-11-29 ?? ?? 01:23?? Dominik Vogt ?? On Fri, Nov 26, 2004 at 10:51:54AM +0800, David Sun wrote: Hi all I'm planning to customize the Start Menu on the taskbar based on fvwm 2.4.18.The thing I would like to do is: when people left-mouse-click on the Start Menu, fvwm will look for certain place on local disk for some certain files, and spawn the menu on the fly according to the lookup result. Could you please advise which files/functions I should look into? Take a look at the DynamicPopUpAction menu option and the fvwm-menu-directory script. thanks for your advice, unfortuantely, my target machine is too size-limited to have perl. I have achieved the purpose by playing with the FvwmTaskBar code which get called when the Start button is pressed And how can I look into a running FVWM for what call-chains are performed when certain event happens? The more detailed is more appreciated^_^ You can attach a debugger to the running fvwm process from a console or a second X server (*not* from the X server running fvwm). With gdb: $ gdb fvwm processid Ciao Dominik ^_^ ^_^ -- Dominik Vogt, [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]
Re: Fvwm bug 1135 keysym documentation, not a bug
On Fri, Nov 26, 2004 at 09:35:06PM -0500, Dan Espen wrote: I've closed this problem as not a bug. you seem to miss the point. I found this comment in the keysymdef.h from the current Xorg release: ! The definitions here should match X11/XF86keysym.h XF86AudioLowerVolume :1008FF11 This can't be in keysymdef.h ; it's in XKeysymDB. XKeysymDB is a better reference to look into, IMHO, when looking for keysyms. The point is that not only the entries from keysymdef.h can be used, but also those from XF86keysym.h (with XK_ stripped out in the middle) ; The alternative I suggest is to direct the user to XKeysymDB instead, which contains all possible keysyms with correct spelling. Note that as the man page currently contains no reference to XKeysymDB, it's not obvious that one should look into it. E. -- 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]
Re: Fvwm bug 1135 keysym documentation, not a bug
Emmanuel Thomé [EMAIL PROTECTED] writes: On Fri, Nov 26, 2004 at 09:35:06PM -0500, Dan Espen wrote: I've closed this problem as not a bug. you seem to miss the point. I found this comment in the keysymdef.h from the current Xorg release: ! The definitions here should match X11/XF86keysym.h XF86AudioLowerVolume:1008FF11 This can't be in keysymdef.h ; it's in XKeysymDB. XKeysymDB is a better reference to look into, IMHO, when looking for keysyms. The point is that not only the entries from keysymdef.h can be used, but also those from XF86keysym.h (with XK_ stripped out in the middle) ; The alternative I suggest is to direct the user to XKeysymDB instead, which contains all possible keysyms with correct spelling. Note that as the man page currently contains no reference to XKeysymDB, it's not obvious that one should look into it. I think you missed my point. From the header file, I surmised that the X developers mean to keep XKeysymDB and keysymdef.h in sync. It looks like they've failed. What you have is a bug in X, not in Fvwm. I believe removing the XK_ from the middle is also a bug. This whole thing with X keysyms is bad enough (using a header file as documentation). It shouldn't get any worse than it is. (Just my opinion.) -- Dan Espen E-mail: [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]
Re: Fvwm bug 1135 keysym documentation, not a bug
Emmanuel Thomé [EMAIL PROTECTED] writes: On Fri, Nov 26, 2004 at 09:35:06PM -0500, Dan Espen wrote: I've closed this problem as not a bug. you seem to miss the point. I found this comment in the keysymdef.h from the current Xorg release: ! The definitions here should match X11/XF86keysym.h XF86AudioLowerVolume:1008FF11 This can't be in keysymdef.h ; it's in XKeysymDB. XKeysymDB is a better reference to look into, IMHO, when looking for keysyms. The point is that not only the entries from keysymdef.h can be used, but also those from XF86keysym.h (with XK_ stripped out in the middle) ; The alternative I suggest is to direct the user to XKeysymDB instead, which contains all possible keysyms with correct spelling. Note that as the man page currently contains no reference to XKeysymDB, it's not obvious that one should look into it. Sorry, the man page for xmodmap explains it this way: The KEYSYMNAME on the left hand side is translated into matching keycodes used to perform the corre sponding set of keycode expressions. The list of keysym names may be found in the header file X11/keysymdef.h (without the XK_ prefix) or the keysym database/usr/X11R6/lib/X11/XKeysymDB. Note that if the same keysym is bound to multiple keys, the expression is executed for each matching keycode. They still refer to an XK_ prefix, but it looks like having 2 files to refer to is intentional. I'll update the man page. -- Dan Espen E-mail: [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]
shape masking and it's future in fvwm
Hello devs, great work on fvwm. I was wondering what the future of shape masking in Fvwm will be. I've noticed a few things about it currently that don't sit well with me, and I wondered if anyone was still working on this portion of fvwm and of course, if they were willing to take some suggestions: 1. Shape masking doesn't work in title bars as of yet, although you can use pixmaps to shape yourself some rounded (or otherwise different) corners, if you don't use pixmaps you are left with no choices. 2. Shape masking ruins the effect borders have in Fvwm. Example: I make a shape mask for my menu and when I bring up the menu I have shaped corners, the problem is, the border around the menu window is cut off where the shaping happens. Will it ever be possible for the border to follow the contour of the shape mask? Thanks in advance, -Evan [EMAIL PROTECTED] hednod @ #fvwm irc.freenode.net -- 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]
