Re: 8-bit vs. 24-bit on new Sun hardware.

Martin> An application running in this kind of environment should be able to Martin> recognize that the display is truly 24-bit and create 24-bit windows. Martin> For example, recent netscape's do this properly. Martin> xwininfo on a netscape window: Depth: 24 Visual Class: TrueColor Martin> xwininfo on a xemacs window: Depth: 8 Visual Class: PseudoColor dv> I don't quite understand what you mean here. If you're running under a dv> TrueColor 24 visual BY DEFAULT and don't mess up with it (neither with the dv> colormap), you simply get windows of the same visual. Here, your X server was dv> probably not launched with TrueColor24 by default, and I wouldn't be surprised dv> that netscape comes with the --install option (and a private colormap). Again, most Sun customers won't change the default visual from the factory default. Most xemacs users won't use the -visual command line option. dv> If you're telling us that /regardless/ of the default visual, XEmacs dv> should use the best one by default, I strongly disagree. For instance, if you dv> have PseudoColor8 by default and force XEmacs to use TrueColor24, you'll get dv> colormap flashing because it needs a different one (remeber there's a strong dv> relation between the visual you choose and the colormaps you can use) and user dv> scream :-) I don't get flashing when one app is in 8-bit PseudoColor mode and the other app is in 24-bit TrueColor mode. netscape simply seems to do The Right Thing. We should too. dv> On the other hand, you can use the -visual option to change the dv> default visual. BTW, I'd be curious to see if XEmacs is clever enough, when dv> given the -visual option, to figure out whether he needs a private colormap dv> too... No private colormap. No flashing. Caveat: I don't really understand X11 visuals. Martin