Mikhael Goikhman <[EMAIL PROTECTED]> writes: > On 18 Jul 2002 11:07:51 +0100, Tim Phipps wrote: > > > > > But, when I run my Xserver with depth > > > 8 (and fvwm allocate these 216 colors) I *cannot* reproduce any > > > problems, I can run netscape, xv, gimp, any gtk/gnome apps, any > > > kde apps ..etc without any problems. > > > > You may be being helped by your graphics card/Xserver. If your setup > > allows other colormaps to be active without deactivating the root > > colormap then it could be that netscape etc have allocated a private > > colormap and you don't notice. Other people on less advanced hardware will.
Never heard of multiple 8 bit color maps except some references to overlay planes, but I don't know much about them. > > It could be that your apps are sophisticated enough to cope with low > > availability of colors. There are plenty of ancient CAD applications > > around that fall over in a big heap if they don't get every color they > > ask for. Framemaker refuses to start if it can't get the colors it wants. I have to run other locally developed apps that do the same thing. > What Dan and Tim say is that there is old hardware and old applications > that cause a lot of color problems. > > What Olivier says is that on modern hardware and with modern applications > FVWM looks better using a new colormap table method (no black colors for > new colors anymore). And he wants to keep an FVWM color limit centrally. I'm not sure what "modern hardware" means. 8 bit colormaps aren't modern. >From the description, gradients still didn't look good. Having the window manager take almost all of a scarce resource doesn't sound like a reasonable way to go. > So maybe a solution is to find the correct condition to activate one or > another code. Or just leave it the way it is now, but print a warning on > the ColorLimit command saying it is now replaced with $FVWM_COLOR_LIMIT. I can't say I like the last option. In my opinion, the old way works. > On 18 Jul 2002 06:56:12 -0400, Dan Espen wrote: > > > > I would not expect to be able to use tinting or > > gradients on an 8 bit display. > > It may be not an option for a user. For example, he uses someone else's > configuration (fvwm-themes), or his own configuration from another > hardware. He may expect the same config automagically to look tolerably > well even on another hardware. If you remember the mini-themes package I posted a while back, it used cpp to eliminate the gradients in 8 bit environments. Shouldn't fvwm-themes be doing something similar? > Of course, I myself don't run neither 8bpp nor old hardware, so ignore my > comments if they make no sense. I've coped with 8 bit for years and years. The ColorLimit command helped a whole lot getting icons under control and making Fvwm attractive. I admit, I finally gave up, mainly because my Sun hardware wouldn't go to 1600x1200 and I now use Linux for my home and work desktop. The users I support at work are still mostly on 8 bit hardware. -- Dan Espen E-mail: [EMAIL PROTECTED] 444 Hoes Lane Room RRC 1C-214 Phone: (732) 699-5570 Piscataway, NJ 08854 -- 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]
