incorrect bg average
I am a bit puzzled with background/lightsky.png from fvwm-themes cvs. It is bluish, without any red, but when I do: Colorset 14 Pixmap background/lightsky.xpm, bg average, fg contrast $[bg.cs14] becomes red - rgb:7272/2d2d/4c4c. If save this 400x300 image scaled to 75% or less, bg becomes blue. But if I scale it to 90%, it is still red. Converting to xpm does not change results. Does someone know how this is possible? 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: Stroke Functionality
On Thu, May 23, 2002 at 09:28:39AM -0400, Daniel Henninger wrote: I'm not sure what I'm going to come up with yet, but is anyone working with Stroke right now and does anyone mind some possible enhancements in it's behavior? Feel free to make patches there (but remember to use the latest code from CVS to start with). 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]
CVS domivogt fvwm-web: * Added a link.
CVSROOT:/home/cvs/fvwm Module name:fvwm-web Changes by: domivogt02/05/26 10:45:39 Modified files: . : ChangeLog links.html Log message: * Added a link. -- 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]
readability of shadow text
I wonder if it's possible to improve the readability of shadow text a bit. With my default palette (pale blue window titles, orange title on the focused window, black text), it's quite difficult to read the title. Two ideas to improve the situation: - Better contrast between shadow and text colours. Probably won't help much. - Offset the shadow text by another pixel E.g. XX X X XX . X .X . X .X . . .. Instead of XX X X . XX . X .X X . X .. 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]
CVS migo fvwm-web: * mention that Suzanne configs only work in 2.5.0, not 2.5.1 to avoid questions
CVSROOT:/home/cvs/fvwm Module name:fvwm-web Changes by: migo02/05/26 11:06:32 Modified files: . : ChangeLog links.html Log message: * mention that Suzanne configs only work in 2.5.0, not 2.5.1 to avoid questions * removed unexisting fvwm.themes.org link -- 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: readability of shadow text
On 26 May 2002 17:18:57 +0200, Dominik Vogt wrote: I wonder if it's possible to improve the readability of shadow text a bit. With my default palette (pale blue window titles, orange title on the focused window, black text), it's quite difficult to read the title. Two ideas to improve the situation: - Better contrast between shadow and text colours. Probably won't help much. Black text is not very good for shadowing, but this depends on font. Try white text with your palettes. It looks very well. Ideally shadow should enable more text colors to be readable on any bg. I got very good results without changing the default fgsh calculations with both black text and white text in your theme. Try: Style * Font shadowsize=3:xft:Luxi Sherif:Bold:size=13 Shadow size 2 is good too (and shadow size 1 with white). - Offset the shadow text by another pixel E.g. XX X X XX . X .X . X .X . . .. Instead of XX X X . XX . X .X X . X .. Hmm, I though this will be even more ugly, but I am not sure now. I patched the source (currently lines 1009-1010 in Flocale.c) and offset 2 looks good with bold or Xft fonts, but not with others. So, probably we may add a third argument to shadow: shadow=size[,directions[,offset]] I also want to see whether shadow=1,br+b is ugly or not. Something like: XX .X X.. .XX.. X..X X.. .X .. .. 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 random focus w/ Alt-Tab. Warning: may cause other focus problems.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/05/26 14:55:26 Modified files: . : ChangeLog fvwm : add_window.c events.c focus.c focus.h fvwm.c screen.h Log message: * Fixed random focus w/ Alt-Tab. Warning: may cause other focus problems. * Fixed decoration drawing after restart on desk != 0. -- 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: Default Alt-Tab does not focuses
On Fri, Apr 26, 2002 at 08:42:53PM +, Mikhael Goikhman wrote: Gee, why I notice problems _after_ release. With no config file. Open 2 xterm (or FvwmConsole). Press Alt-Tab-Tab, release Alt. The pointer is warped, but not the focus. This is fixed now. This wasn't new to 2.5.x, though. It should have happened in 2.4.x too. It was one of these pesky race conditions between EnterNotify events generated by moving or grabbing/releasing the pointer and calling Focus or FlipFocus in parallel. With my change, EnterNotify events are now ignored after one of these two commands until the next FocusIn event arrives. This should lessen the probability of future race contitions with the focus, but may cause problems elsewhere. Please keep your eyes open. 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]
Re: Restart from non desk 0 does not decorate
On Fri, Apr 26, 2002 at 08:46:27PM +, Mikhael Goikhman wrote: Do Restart without parameters from non first desk. Any existing windows are not (correctly) decorated until the pointer enters them. Reproducible with no config too. Just open xterm on Desk 1 and Restart. No idea what cause this, but I now force drawing the window decorations when a window is mapped. With the new frame drawing code, this shouldn't be much overhead. 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]
Re: readability of shadow text
On Sun, May 26, 2002 at 05:26:40PM +, Mikhael Goikhman wrote: On 26 May 2002 17:18:57 +0200, Dominik Vogt wrote: I wonder if it's possible to improve the readability of shadow text a bit. With my default palette (pale blue window titles, orange title on the focused window, black text), it's quite difficult to read the title. Two ideas to improve the situation: - Better contrast between shadow and text colours. Probably won't help much. Black text is not very good for shadowing, but this depends on font. Try white text with your palettes. It looks very well. Ideally shadow should enable more text colors to be readable on any bg. I got very good results without changing the default fgsh calculations with both black text and white text in your theme. Try: Style * Font shadowsize=3:xft:Luxi Sherif:Bold:size=13 Shadow size 2 is good too (and shadow size 1 with white). Hm, I see no big difference with lucidasanstypewriter-12. I took a closer look: what really irritates me is that the shadows fill the inside of some letters, like O: XXX X X X ..X X. X. X. X. XXX . . . ... I think it might look better if the shadow is limited to the area not covered by the regular text: XXX X X X X X X X X XXX . . ... This could be an option. - Offset the shadow text by another pixel E.g. XX X X XX . X .X . X .X . . .. Instead of XX X X . XX . X .X X . X .. Hmm, I though this will be even more ugly, but I am not sure now. I patched the source (currently lines 1009-1010 in Flocale.c) and offset 2 looks good with bold or Xft fonts, but not with others. So, probably we may add a third argument to shadow: shadow=size[,directions[,offset]] I also want to see whether shadow=1,br+b is ugly or not. Something like: XX .X X.. .XX.. X..X X.. .X .. .. 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]
Re: Shadow Text
On Sat, May 25, 2002 at 12:00:23AM +, Mikhael Goikhman wrote: On 24 May 2002 19:30:26 -0400, Dan Espen wrote: Olivier Chapuis [EMAIL PROTECTED] writes: On Thu, May 23, 2002 at 05:15:28AM +, Mikhael Goikhman wrote: And I think what we need is this: shadow=size[,direction] Yes, I am agree. One point is that I do not think that we need distincts x and y (Dan?). I don't know whether specifying more than 1 direction (more than 1 bit) looks good, say 3 directions [n, ne, e] are encoded by 2+4+8=14. But I know that a shadow _around_ text should look nice: shadow=1,255 This draws a shadow 8 times, one in each direction. Just an idea. Yes agree again. But do you think that the user will like to give the directions with a number? So the syntax may be: shadow=size [directions] where directions is a space separated list constituted by se (default), s, n, o, e, so, ne, no and all. Or maybe we can use iconbox directions bl, b, t, l, r, br, tr, tl. Lets see, a 1 pixel shadow on the upper right would be: Font shadow=1,ur:9x15bold A 2 pixed shadow all around the character would be: Font shadow=2,l r t b ur ul lr ll:9x15bold Just to make it sure we all agree. I think comma to separate size and direction is better than space. A space or a plus may separate directions. I think the all name is ok. I've chosen to do not use , but space between size and direction. First , are used in the XLFD to separated different fonts. So it seems to me that a , denote an alternative in font name. Also it seems to me that , is a strong separator from fvwm syntax point of view. About directions. I've used l r u b ur ul br bl. Is u alone should be t? 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: readability of shadow text
On Sun, May 26, 2002 at 10:01:27PM +0200, Dominik Vogt wrote: On Sun, May 26, 2002 at 05:26:40PM +, Mikhael Goikhman wrote: On 26 May 2002 17:18:57 +0200, Dominik Vogt wrote: I wonder if it's possible to improve the readability of shadow text a bit. With my default palette (pale blue window titles, orange title on the focused window, black text), it's quite difficult to read the title. Two ideas to improve the situation: - Better contrast between shadow and text colours. Probably won't help much. Black text is not very good for shadowing, but this depends on font. Try white text with your palettes. It looks very well. Ideally shadow should enable more text colors to be readable on any bg. I got very good results without changing the default fgsh calculations with both black text and white text in your theme. Try: Style * Font shadowsize=3:xft:Luxi Sherif:Bold:size=13 Shadow size 2 is good too (and shadow size 1 with white). Hm, I see no big difference with lucidasanstypewriter-12. I took a closer look: what really irritates me is that the shadows fill the inside of some letters, like O: XXX X X X ..X X. X. X. X. XXX . . . ... I think it might look better if the shadow is limited to the area not covered by the regular text: XXX X X X X X X X X XXX . . ... Yes this will be good, but ... This could be an option. I do not see how to implement this in a simple way. It seems to me that such rendering should be handled at an other level than the fvwm library level. 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: readability of shadow text
On Sun, May 26, 2002 at 05:26:40PM +, Mikhael Goikhman wrote: On 26 May 2002 17:18:57 +0200, Dominik Vogt wrote: I wonder if it's possible to improve the readability of shadow text a bit. With my default palette (pale blue window titles, orange title on the focused window, black text), it's quite difficult to read the title. Two ideas to improve the situation: - Better contrast between shadow and text colours. Probably won't help much. Black text is not very good for shadowing, but this depends on font. Try white text with your palettes. It looks very well. Ideally shadow should enable more text colors to be readable on any bg. I got very good results without changing the default fgsh calculations with both black text and white text in your theme. Try: Style * Font shadowsize=3:xft:Luxi Sherif:Bold:size=13 Shadow size 2 is good too (and shadow size 1 with white). - Offset the shadow text by another pixel E.g. XX X X XX . X .X . X .X . . .. Instead of XX X X . XX . X .X X . X .. Hmm, I though this will be even more ugly, but I am not sure now. I patched the source (currently lines 1009-1010 in Flocale.c) and offset 2 looks good with bold or Xft fonts, but not with others. So, probably we may add a third argument to shadow: shadow=size[,directions[,offset]] shadow=size [offset] directions seems more logic for me. I also want to see whether shadow=1,br+b is ugly or not. Something like: XX .X X.. .XX.. X..X X.. .X .. .. So ? 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 migo fvwm-web: * mention that Suzanne configs only work in 2.5.0, not 2.5.1 to avoid questions
FVWM CVS wrote: * removed unexisting fvwm.themes.org link Someone may want to add the new link to themes.freshmeat.net's section for fvwm at http://themes.freshmeat.net/browse/929/?topic_id=929 Just a thought. Alex -- 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: readability of shadow text
On 26 May 2002 22:39:58 +0200, Olivier Chapuis wrote: On Sun, May 26, 2002 at 05:26:40PM +, Mikhael Goikhman wrote: On 26 May 2002 17:18:57 +0200, Dominik Vogt wrote: I wonder if it's possible to improve the readability of shadow text a bit. With my default palette (pale blue window titles, orange title on the focused window, black text), it's quite difficult to read the title. Two ideas to improve the situation: - Better contrast between shadow and text colours. Probably won't help much. Black text is not very good for shadowing, but this depends on font. Try white text with your palettes. It looks very well. Ideally shadow should enable more text colors to be readable on any bg. I got very good results without changing the default fgsh calculations with both black text and white text in your theme. Try: Style * Font shadowsize=3:xft:Luxi Sherif:Bold:size=13 Shadow size 2 is good too (and shadow size 1 with white). - Offset the shadow text by another pixel E.g. XX X X XX . X .X . X .X . . .. Instead of XX X X . XX . X .X X . X .. Hmm, I though this will be even more ugly, but I am not sure now. I patched the source (currently lines 1009-1010 in Flocale.c) and offset 2 looks good with bold or Xft fonts, but not with others. So, probably we may add a third argument to shadow: shadow=size[,directions[,offset]] shadow=size [offset] directions seems more logic for me. I have no objection. Although I don't see how it would be possible to extend such syntax in the future, for example add outside-only boolean. I also want to see whether shadow=1,br+b is ugly or not. Something like: XX .X X.. .XX.. X..X X.. .X .. .. So ? Yes, br b seems better than just br with good font and white text. :) As I expected 1 all gives really fun results, say: fg yellow, fgsh black But it seems it makes sense to use more than 1 direction only with size=1, otherwise the shadow is strewn, especialy with big sizes. I think we may forse size=1 when more than 1 from 8 directions specified. Or invent 24 (16) directions for size=2; 48 (24) directions for size=3... Thank you. :) 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: Shadow Text
On Sun, May 26, 2002 at 10:27:28PM +0200, Olivier Chapuis wrote: About directions. I've used l r u b ur ul br bl. Is u alone should be t? Don't forget that there is already a direction parsing function in libs/gravity.c that can be easily extended to handle 't', 'u', ... 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]
CVS domivogt: * Implemented NoBorder/Border styles.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/05/26 16:47:32 Modified files: . : ChangeLog NEWS fvwm : add_window.c borders.c decorations.c frame.c fvwm.1 fvwm.h module_interface.c style.c style.h window_flags.h modules: ChangeLog modules/FvwmCommand: FvwmCommand.c modules/FvwmDebug: FvwmDebug.c Log message: * Implemented NoBorder/Border styles. -- 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 domivogt: * Implemented NoBorder/Border styles.
On 26 May 2002 16:47:32 -0500, FVWM CVS wrote: Log message: * Implemented NoBorder/Border styles. Ok, here is a new MaximizeFullScreen function: DestroyFunc MaximizeFullScreen AddToFunc MaximizeFullScreen + I ThisWindow (Maximized) Style $n Title, Border + I CondCase (NoMatch) Style $n NoTitle, NoBorder + I CondCase (NoMatch) Raise + I CondCase (NoMatch) UpdateStyles + I Maximize Key F11 A SC Pick MaximizeFullScreen Conditions HasBorder and HasTitle would help to restore the original settings (that are stored in 2 window State-s). I thought names NoBorders/Borders would be more logical if we have four individual borders, but this is not very important. 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: * Removed --enable-multibyte option.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/05/26 18:45:43 Modified files: . : ChangeLog NEWS acconfig.h configure.in fvwm : fvwm.c libs : Flocale.h fvwmlib.h modules: ChangeLog modules/FvwmCpp: FvwmCpp.c modules/FvwmIconMan: xmanager.h modules/FvwmM4 : FvwmM4.c Log message: * Removed --enable-multibyte option. * Fixed a key binding problem. -- 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 a key binding problem.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/05/26 18:46:06 Modified files: . : Tag: branch-2_4 ChangeLog NEWS fvwm : Tag: branch-2_4 fvwm.c Log message: * Fixed a key binding problem. -- 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]
2.4.8 release time?
I think we've collected enough fixes for another stable release. Any volunteers to do the release? 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]
CVS domivogt: * TMPDIR safety patch by Jan Echternach.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/05/26 19:21:21 Modified files: . : AUTHORS ChangeLog fvwm : add_window.c focus.c session.c modules: ChangeLog modules/FvwmCpp: FvwmCpp.c modules/FvwmM4 : FvwmM4.c Log message: * TMPDIR safety patch by Jan Echternach. * Colormap focus fix. -- 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: * TMPDIR safety patch by Jan Echternach.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt02/05/26 19:21:40 Modified files: . : Tag: branch-2_4 AUTHORS ChangeLog NEWS fvwm : Tag: branch-2_4 focus.c session.c modules/FvwmCpp: Tag: branch-2_4 FvwmCpp.c modules/FvwmM4 : Tag: branch-2_4 FvwmM4.c Log message: * TMPDIR safety patch by Jan Echternach. * Colormap focus fix. -- 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/875
On Wed, Apr 17, 2002 at 05:15:28PM -0500, fvwm-bug wrote: FVWM Bug Tracking notification new message incoming/875 Full_Name: Jan Echternach Version: 2.4.7 CVS_Date: OS: Linux X_Server: XFree86 3.3.6 Submission from: (NULL) (62.104.208.83) tempnam() may use $TMPDIR. If that directory is writable by other users, a temporary file may be created insecurely. I'm attaching a simple patch that also uses getpwuid() more carefully, and looks at $HOME as the fvwm2.1 man page describes. Note 1: The patch compiles, but I haven't tested it because I don't use session management. Note 2: The man page doesn't mention TMPDIR, maybe this should be fixed as well. Note 3: FvwmCpp.c and FvwmM4.c also create temporary files, but with mode 0644. I think this should be changed to 0600. Thanks for the patch. I have committed it to the development code. If it works fine, I'll add it to the stable branch too. 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]
Re: Notification: incoming/876
On Wed, Apr 17, 2002 at 05:34:05PM -0500, fvwm-bug wrote: FVWM Bug Tracking notification new message incoming/876 Full_Name: Jan Echternach Version: 2.4.7 CVS_Date: OS: Linux X_Server: XFree86 3.3.6 Submission from: (NULL) (62.104.208.83) Szenario: netscape uses a private colormap. A transient window is opened (e.g. the Find dialog with Alt+F), also with a private colormap. This new window gets the focus even if the pointer (FocusFollowsMouse) is not inside it. Esc is pressed to close the transient window. Case 1: Pointer is in the transient window: no problem. Case 2: Pointer is outside the transient window, but inside the main netscape window: The colormap of the main window won't be restored properly, even though it gets the focus and the pointer is inside it. Should be fixed with the next release. Could you please try the latest CVS code or tomorrow's snapshot and report back if the problem goes away? 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]
Re: 2.4.8 release time?
On Mon, May 27, 2002 at 01:46:30AM +0200, Dominik Vogt wrote: I think we've collected enough fixes for another stable release. Any volunteers to do the release? Better wait for a couple of days. I'm not sure if my latest patches are good. 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]
