CVS olicha: * Clip text and icon drawing for the fvwm icons
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: olicha 02/09/23 02:40:13 Modified files: . : ChangeLog fvwm : add_window.c borders.c events.c geometry.c icons.c icons.h update.c libs : FRender.c Rectangles.c Rectangles.h modules: ChangeLog modules/FvwmButtons: FvwmButtons.c draw.c draw.h dynamic.c Log message: * Clip text and icon drawing for the fvwm icons * Fixed(?) XRender rendering with some Xserver * Some preparation for clipping in FvwmButtons -- 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: CVS olicha: * A Transparent and clipping patch
On Sat, Sep 21, 2002 at 11:33:43AM +, Mikhael Goikhman wrote: On 21 Sep 2002 10:47:44 +0200, Olivier Chapuis wrote: On Fri, Sep 20, 2002 at 10:45:23AM +, Mikhael Goikhman wrote: No, unfortunately this does not fix the problem. Until I execute Tint without parameters, colorset remains Plain. Do Alpha, IconAlpha and IconTint work (independently)? IconAlpha and IconTint work (wow, it is nice). Alpha 50, bg yellow works nicely too. Ok, here may be some clue. Tint green 50, Alpha 99 # (or any value 100) works as expected Tint green 50, Alpha 0 # colorset is Plain, this is ok! Tint green 50, Alpha 100 # colorset is Plain, this is not ok Tint green 50, Alpha # colorset is Plain, this is not ok HHAAA! Ok, now I hope it is fixed. If not there is a so big bug in fvwm that I cannot see it. If yes, IMHO your Xserver is buggy vs XRender. What it is your Xserver? Olivier -- 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: CVS olicha: * A Transparent and clipping patch
On 23 Sep 2002 09:29:31 +0200, Olivier Chapuis wrote: Ok, now I hope it is fixed. If not there is a so big bug in fvwm Yes, it is fixed. that I cannot see it. If yes, IMHO your Xserver is buggy vs XRender. What it is your Xserver? I am not sure what to add to the xdpyinfo output. It is XFree86-4.2.0-6.62 packaged by RedHat. BTW, you do a really fantastic work. Regards, Mikhael. -- 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: CVS migo: * ImagePath now supports directories in form /some/directory;.png
On Sat, Sep 21, 2002 at 04:12:00PM -0500, fvwm-workers wrote: * execcontext.h: use 'M' for EXCT_MODULE not 'O', Actually, I chose 'O' so that we don't have two 'm', 'M' contexts, which can be confusing. That menus still had the lower case 'm' was a mistake, but I don't care much. use 'I'nit for EXCT_NULL Originally I had a 'startup' context but gave it up because it could not be defined well. But calling the NULL context Init is not right. It applies to many other situations too that are not even remotely related to initialization. Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe -- 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: locale error messages
On Fri, Sep 20, 2002 at 08:33:34PM -0400, Bruce M Beach wrote: On Fri, 20 Sep 2002, Dominik Vogt wrote: What do these error messages try to tell me: -- [FvwmButtons][FlocaleSetlocaleForX]: ERROR -- Cannot set locale. Please check your $LC_CTYPE or $LANG. [FvwmPager][FlocaleSetlocaleForX]: ERROR -- Cannot set locale. Please check your $LC_CTYPE or $LANG. Warning: locale not supported by C library, locale unchanged [FvwmPager][FlocaleSetlocaleForX]: ERROR -- Cannot set locale. Please check your $LC_CTYPE or $LANG. [FvwmIconMan][FlocaleSetlocaleForX]: ERROR -- Cannot set locale. Please check your $LC_CTYPE or $LANG. Warning: locale not supported by C library, locale unchanged -- This is what I have set: $ locale LANG=C [EMAIL PROTECTED] ... LC_*=C ... LC_ALL= Does [EMAIL PROTECTED] actually exist? For instance locate [EMAIL PROTECTED] $ locate [EMAIL PROTECTED] /usr/lib/locale/[EMAIL PROTECTED] /usr/lib/locale/[EMAIL PROTECTED]/LC_ADDRESS /usr/lib/locale/[EMAIL PROTECTED]/LC_COLLATE /usr/lib/locale/[EMAIL PROTECTED]/LC_CTYPE /usr/lib/locale/[EMAIL PROTECTED]/LC_IDENTIFICATION /usr/lib/locale/[EMAIL PROTECTED]/LC_MEASUREMENT /usr/lib/locale/[EMAIL PROTECTED]/LC_MESSAGES /usr/lib/locale/[EMAIL PROTECTED]/LC_MESSAGES/SYS_LC_MESSAGES /usr/lib/locale/[EMAIL PROTECTED]/LC_MONETARY /usr/lib/locale/[EMAIL PROTECTED]/LC_NAME /usr/lib/locale/[EMAIL PROTECTED]/LC_NUMERIC /usr/lib/locale/[EMAIL PROTECTED]/LC_PAPER /usr/lib/locale/[EMAIL PROTECTED]/LC_TELEPHONE /usr/lib/locale/[EMAIL PROTECTED]/LC_TIME /usr/share/i18n/locales/[EMAIL PROTECTED] should give you a whole bunch of stuff. If you build the libraries yourself then glibc doesn't install all the locales by default but you have to do a make localedata/install-locales after 'make install' The guys on the i18n@XFree86.Org mailing list will help if you email them. I just installed the German language package from Debian 3.0. Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe -- 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: locale error messages
On Sat, Sep 21, 2002 at 07:04:39AM +0200, Olivier Chapuis wrote: On Fri, Sep 20, 2002 at 04:12:22PM +0200, Dominik Vogt wrote: What do these error messages try to tell me: -- [FvwmButtons][FlocaleSetlocaleForX]: ERROR -- Cannot set locale. Please check your $LC_CTYPE or $LANG. [FvwmPager][FlocaleSetlocaleForX]: ERROR -- Cannot set locale. Please check your $LC_CTYPE or $LANG. Warning: locale not supported by C library, locale unchanged [FvwmPager][FlocaleSetlocaleForX]: ERROR -- Cannot set locale. Please check your $LC_CTYPE or $LANG. [FvwmIconMan][FlocaleSetlocaleForX]: ERROR -- Cannot set locale. Please check your $LC_CTYPE or $LANG. Warning: locale not supported by C library, locale unchanged -- This is what I have set: $ locale LANG=C [EMAIL PROTECTED] It means that the libc function setlocale return a NULL pointer when it is call as setlocale(LC_TYPE, ). My libc manual says that: - Passing means to read the appropriate environment variable and use its value to select the locale for LC_CTYPE. - If you specify an invalid locale name, `setlocale' returns a null pointer and leaves the current locale unchanged. So it seems to me that the locale [EMAIL PROTECTED] is not supported by your libc. This seems strange and IMHO your system is miss-configured. Maybe your locale definitions of [EMAIL PROTECTED] (found somewhere under (/usr/share/locale/) is incomplete or does not match your libc. Maybe you have upgraded your libc without upgrading your locales (or inversely). Sigh! Today the error message is gone without changing anything. Might the setlocale function just throw random results from time to time? Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe -- 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: CVS olicha: * Clip text and icon drawing for the fvwm icons
On 23 Sep 2002 02:40:13 -0500, FVWM CVS wrote: Log message: * Clip text and icon drawing for the fvwm icons Icons are practically do not flicker now when should be partially redrawn. But png icons still flicker *a lot* by merelly focusing/unfocussing them. I think some bug with icon title drawing was introduced. To reproduce it, I restart with no config, then define some Style ** Icon norm/unknown.xpm OpaqueMoveSize unlimited # not really needed to reproduce problems Then iconify several windows from FvwmConsole and select one or another. If you defined xpm icon do: Style * IconBox 0 0 1000 1000, IconFill l t With xpm icon, title bg is incorrect until you focus/unfocus an icon. With png icon, title text randomly disappears/appears when you focus it. Regards, Mikhael. -- 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: Root Key Press
On Fri, Sep 20, 2002 at 11:32:16PM -0700, [EMAIL PROTECTED] wrote: I'm laying out a new module and having a little trouble with XEvents. This might be a purely X issue. I want to catch a key press anywhere on the screen, like the Alt key. It doesn't have to be exclusive. In fact, I want the fvwm core to read the keys too and act as usual. I tried XSelectInput(dpy,rootWindow,KeyPressMask|KeyReleaseMask), but I never get any events. In fact, for the several masks I've tried, the only one that did anything was PointerMotionMask. This tells me my approach is not entirely broken. If I can get this to work, I'm not sure I'll get the event if the mouse is over a non-root window, but that's the next step. I can't think of another module that even reads the keyboard, much less reading keys when not on a window created by the module. You want to use the XGrabKey() function, not just XSelectInput(). Unfortunately the result *is* exclusive. Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe -- 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: CVS migo: * ImagePath now supports directories in form /some/directory;.png
On 23 Sep 2002 11:08:22 +0200, Dominik Vogt wrote: On Sat, Sep 21, 2002 at 04:12:00PM -0500, fvwm-workers wrote: * execcontext.h: use 'M' for EXCT_MODULE not 'O', Actually, I chose 'O' so that we don't have two 'm', 'M' contexts, which can be confusing. That menus still had the lower case 'm' was a mistake, but I don't care much. use 'I'nit for EXCT_NULL Originally I had a 'startup' context but gave it up because it could not be defined well. But calling the NULL context Init is not right. It applies to many other situations too that are not even remotely related to initialization. I used these values, just because I use command-log sometimes and for me I: looks a bit better (and more informative) than -:. I didn't see any of 'I' other than on startup. Why exec context type would not be defined after fvwm enters the event loop? Regards, Mikhael. -- 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]
CVS domivogt: * Fixed menu drawing bug.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/09/23 05:38:23 Modified files: . : Tag: branch-2_4 ChangeLog NEWS fvwm : Tag: branch-2_4 menus.c Log message: * Fixed menu drawing bug. * Fixed accidental menu animation with certain menu position hints. -- 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]
CVS domivogt: * Fixed accidental menu animation with certain menu position hints.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/09/23 05:38:26 Modified files: . : ChangeLog fvwm : menus.c Log message: * Fixed accidental menu animation with certain menu position hints. -- 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]
CVS domivogt: * Added EXCT_INIT and EXCT_EXIT contexts; changed NULL context letter back to -
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/09/23 05:53:20 Modified files: . : ChangeLog fvwm : execcontext.h fvwm.c Log message: * Added EXCT_INIT and EXCT_EXIT contexts; changed NULL context letter back to - -- 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: CVS migo: * ImagePath now supports directories in form /some/directory;.png
On Mon, Sep 23, 2002 at 09:34:41AM +, Mikhael Goikhman wrote: On 23 Sep 2002 11:08:22 +0200, Dominik Vogt wrote: On Sat, Sep 21, 2002 at 04:12:00PM -0500, fvwm-workers wrote: * execcontext.h: use 'M' for EXCT_MODULE not 'O', Actually, I chose 'O' so that we don't have two 'm', 'M' contexts, which can be confusing. That menus still had the lower case 'm' was a mistake, but I don't care much. use 'I'nit for EXCT_NULL Originally I had a 'startup' context but gave it up because it could not be defined well. But calling the NULL context Init is not right. It applies to many other situations too that are not even remotely related to initialization. I used these values, just because I use command-log sometimes and for me I: looks a bit better (and more informative) than -:. I didn't see any of 'I' other than on startup. Why exec context type would not be defined after fvwm enters the event loop? Okay many was a bit exaggerated. Currently, the NULL context is used: * in StartupStuff() * in SetRCDefaults() * in main() when the cfg file is read * in CoerceEnterNotifyOnCurrentWindow() * in the CMD_Schedule call in colorset.c * in the first PlaceWindow() call when a window is added * when the exit function is executed * in HandleMapRequestKeepRaised() when calles to create a tear off menu * when applying window updates in update.c Only the first four are related to initialization. I have added two new contexts for 'I'nit and 'E'xit stuff. Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe -- 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]
CVS domivogt: * Applied TB crash fix by Ben Mathews.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/09/23 06:00:19 Modified files: modules: ChangeLog modules/FvwmTaskBar: Start.c Log message: * Applied TB crash fix by Ben Mathews. -- 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: New member anounces diagnosed bug - (fixed, patchfile attached)
On Sat, Sep 21, 2002 at 10:55:47AM -0400, Ben Mathews wrote:
Rastislav Galia wrote:
Hello, I am new to fvwm-workers. I hope this is the right place to post
technical details.
So - in latest cvs source in fvwm/modules/FvwmTaskBar/Start.c there is bug
in case no Start button attributes are defined in config file. In that
case list of Start buttons is empty, causing null pointer dereference and
crash of the module. The bug was introduced recently (Sep 12-th). I did
patch to solve it by inserting this statement to line 254
if (First_Start_Button-isStartButton == TRUE)
{
if (First_Start_Button-buttonCaption == NULL)
UpdateString((First_Start_Button-buttonCaption), Start);
if (First_Start_Button-buttonIconFileName == NULL)
UpdateString((First_Start_Button-buttonIconFileName),
mini-start.xpm);
}
Anyway, maybe this is not what is intended, but assumption of
non-emptyness of the list is all around the code.
/Rastjo
The attached patch will solve this problem.
Applied.
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382
Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe
--
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]
CVS domivogt: * Increased maximum allowed key symbol name length to 200 characters.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/09/23 06:03:23 Modified files: . : ChangeLog fvwm : bindings.c Log message: * Increased maximum allowed key symbol name length to 200 characters. -- 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]
CVS domivogt: * Increased maximum allowed key symbol name length to 200 characters.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/09/23 06:04:55 Modified files: . : Tag: branch-2_4 ChangeLog NEWS fvwm : Tag: branch-2_4 bindings.c Log message: * Increased maximum allowed key symbol name length to 200 characters. -- 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: Notification: incoming/925
On Sat, Sep 21, 2002 at 05:38:02PM +, Mikhael Goikhman wrote: On 21 Sep 2002 10:04:09 -0500, [EMAIL PROTECTED] wrote: Message summary for PR#925 From: [EMAIL PROTECTED] Subject: Key binding problem Full_Name: Jens Thoms Törring Version: 2.4.0 What I found isn't actually a bug but more king of an annoyance: I can't bind keys like XF86AudioRaiseVolume or XF86AudioLowerVolume. The reason is simple: in bindings.c in function ParseBinding() the maximum length of a key name is restricted to 19 characters (plus one for the trailing '\0'. But both the key names are already 20 chars long. A patch is simple: increase the size of the char array key in ParseBinding() to e.g. 0 and allow lengths of up to 29 characters, i.e. change the line n1 = sscanf(token,%19s,key) to n1 = sscanf(token,%29s,key) As far as I can see this breaks nothing and testing results in correct key bindings also for unusually long key names. This is already fixed in 2.4.6. Try fvwm-2.4.11. Anyway, to have some more safety in the future I have increased the number of allowed letters in a key name to 200. It may never be necessary, but if it is we can save us another bug report. Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe -- 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]
menu posting broken
For several months now the menu posting works incorrectly. Basically only one situation works ok, you post a submenu by clicking on its item and then post its direct submenu. All other situations (post a submenu and then post its parent, or submenu on the same level) are incorrect. Unposting (clicking on the currently posted submenu item for the second time) also does not work as it was. Would be nice to return to the previous consistent functionality. Regards, Mikhael. -- 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: menu posting broken
On Mon, Sep 23, 2002 at 12:15:18PM +, Mikhael Goikhman wrote: For several months now the menu posting works incorrectly. Basically only one situation works ok, you post a submenu by clicking on its item and then post its direct submenu. All other situations (post a submenu and then post its parent, or submenu on the same level) are incorrect. Unposting (clicking on the currently posted submenu item for the second time) also does not work as it was. Would be nice to return to the previous consistent functionality. No problem. I'd really prefer to get these bug reports immediately, though. Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe -- 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]
FvwmIdent does not change layers
For many months now (I think, more than half year) FvwmIdent that called on windows with layer greater than 4 does not change layers as intended. FvwmIdent stays on layer 4 obscured by the original window. The FvwmIdent code itself seems ok, but ReparentNotify seems to not be called the last time I looked. Regards, Mikhael. -- 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]
CVS domivogt: * Fixed posting menus.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/09/23 08:17:32 Modified files: . : ChangeLog fvwm : menus.c Log message: * Fixed posting menus. -- 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: menu posting broken
On Mon, Sep 23, 2002 at 12:15:18PM +, Mikhael Goikhman wrote: For several months now the menu posting works incorrectly. Basically only one situation works ok, you post a submenu by clicking on its item and then post its direct submenu. All other situations (post a submenu and then post its parent, or submenu on the same level) are incorrect. Unposting (clicking on the currently posted submenu item for the second time) also does not work as it was. Would be nice to return to the previous consistent functionality. Fixed. Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe -- 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]
CVS domivogt: * Fixed FvwmIdent event mask.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/09/23 08:41:15 Modified files: modules: ChangeLog modules/FvwmIdent: FvwmIdent.c Log message: * Fixed FvwmIdent event mask. -- 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: FvwmIdent does not change layers
On Mon, Sep 23, 2002 at 12:53:47PM +, Mikhael Goikhman wrote: For many months now (I think, more than half year) FvwmIdent that called on windows with layer greater than 4 does not change layers as intended. FvwmIdent stays on layer 4 obscured by the original window. The FvwmIdent code itself seems ok, but ReparentNotify seems to not be called the last time I looked. Fixed. Somehow these events were deleted from the event mask. Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe -- 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]
Parse library quoting problem
The following command does not work correctly:
Exec xmessage -name 'abc) Iconify' something
All ('ab*) Iconify') Maximize
Regards,
Mikhael.
--
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]
CVS domivogt: * Fixed quoting in conditional commands.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/09/23 09:16:03 Modified files: . : ChangeLog fvwm : conditional.c Log message: * Fixed quoting in conditional commands. -- 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]
CVS domivogt: Fixed quotes in conditional commands.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/09/23 09:18:05 Modified files: . : Tag: branch-2_4 ChangeLog NEWS fvwm : Tag: branch-2_4 conditional.c Log message: Fixed quotes in conditional commands. -- 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: Parse library quoting problem
On Mon, Sep 23, 2002 at 02:02:17PM +, Mikhael Goikhman wrote:
The following command does not work correctly:
Exec xmessage -name 'abc) Iconify' something
All ('ab*) Iconify') Maximize
Hey, you scared me for a moment. Fortunately, the bug was in
conditional.c. Fixed.
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382
Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe
--
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: Menu Trouble with FVWM 2.4.10
On Sat, Sep 21, 2002 at 02:16:32AM +0200, Andreas M. Kirchwitz wrote: Hi FVWM Workers! I installed version 2.4.10 of FVWM (on Linux 2.4.19, XFree86 4.1.0, Intel-based; basically a RedHat 7.2 system) and had mysterious troubles with menus. On my left mouse button, I have a menu on my root window which has sub-menus (which has sub-menus itself). Well, I think that's the typical configuration nearly all people have. ;-) Most of the menu entries come with small images, and the menu background is a pixmap. The MenuStyle seetings look like this (if this is of any help): MenuStyle * Win, Hilight3DThin, Animation MenuStyle * Font -*-helvetica-bold-r-*-*-10-*-*-*-*-*-*-* MenuStyle * Foreground White, Background #bb7070 MenuStyle * Greyed SlateGrey, TitleUnderlines2, TrianglesRelief MenuStyle * VerticalItemSpacing 1 5, VerticalTitleSpacing 4 4 MenuStyle * MenuFace TiledPixmap /usr/local/include/X11/pixmaps/texture2.xpm The problem now is that menu entries magically disappear and reappear while the menu (or a sub-menu) is open. I move the mouse through the entries, and magically some text entries disappear (like transparent text, only the background pixmap is seen). While moving the mouse through the entries, certain entries disappear and reappear (it's reproducible). I know, this may sound silly to you but I don't know of a better way to describe this. The problem is clearly related to the changes in fvwm/menus.c between version 2.4.9 and 2.4.10. If I replace the new file (from 2.4.10) with the old file (from 2.4.9) and recompile fvwm2, the menus work great. I can send you my .fvwm2rc file if that is of help to you, or I can try out things in fvwm/menus.c for debugging purposes. Whatever is of help to you to find out what the problem is ... I can reproduce the problem and have already committed a fix. I won't a new release just for this problem immediately, though. If it bothers you too much, just downgrade to 2.4.9 and wait until 2.4.12 is released. But you shouldn't stick with 2.4.10 as it has a nasty core dump (fixed in 2.4.11). Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe -- 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]
CVS dane: * FvwmButtons/FvwmButtons.1:
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: dane02/09/23 12:45:27 Modified files: modules: ChangeLog modules/FvwmAnimate: FvwmAnimate.1 modules/FvwmAuto: FvwmAuto.1 modules/FvwmBacker: FvwmBacker.1 modules/FvwmBanner: FvwmBanner.1 modules/FvwmButtons: FvwmButtons.1 Log message: * FvwmButtons/FvwmButtons.1: * FvwmBacker/FvwmBacker.1: * FvwmAuto/FvwmAuto.1: * FvwmAnimate/FvwmAnimate.1: Rework synopsis. -- 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]
