On Wednesday 16 April 2003 07:04, Maurice LeBrun wrote:
| Joao Cardoso writes:
| > The common solution is to tell those users to define
| > USE_DEFAULT_VISUAL in xwin.c.
| > It seems that all those users are using X terminals that support
| > *simultaneously* 8 bit Pseudo Color and 16/24 bits True Color
| > visuals (one of them also had Static Color). I couldn't reproduce
| > the problem, because XFree can't use simultaneously both kind of
| > visuals. Even if using Xnest. So, the question is: shouldn't we
| > define USE_DEFAULT_VISUAL in xwin.c? It seems to make no
| > difference in my system. And in yours?
| > Maurice, you was the one still using 8 bit Pseudo Color visuals a
| > couple of years ago. What do you think of this issue?
| It was my plan to recode this section of the xwin driver, such that
| it always uses the default visual, unless overridden by a -drvopt
| flag. I think the default visual makes for a fine default, probably
| more useful than the way we do it now. And the -drvopt support means
| that one can always "fix" it at runtime, or at least debug it easier.
| In addition for displays that support multiple visuals it is a nice
| plus to the user to be able to select it at runtime. Should probably
| provide a configuration option to use the legacy approach, but also
| in that case have it be overridden by use of -drvopt.
| Anyway, I'd planned on doing this work nearly a year ago, and am now
| much busier than I was then, so if someone else wants to take a whack
| at it please feel free.
I can try to get time to add a "-drvopt defvis" option to xwin, that
just turns on/off the driver code section now conditionally commented.
The default will still be the same as is now, just to be on the right
side of the fence.
Better than nothing.