On Thu, Oct 03, 2002 at 11:03:27AM +0200, Olivier Chapuis wrote:
> On Wed, Oct 02, 2002 at 05:41:44PM -0700, Tim Freedom wrote:
>
> > And in the "XV Controls" window it notes using "24-bit mode. Using TrueColor
> > visual" meaning the solaris Xserver (Xsun) is capable of 24-bit. So I asked
> > a sys-admin friend and he noted that "xdpyinfo is probably unable to
> > understand 8+24 mode and is simply returning the first result it sees when
> > multiple options are available." So I'm not sure how fvwm determines what
> > the X-server is capable of, but its figuring them to be 8-bit on this
> > machine when they really need to be 24-bit (is it grabbing xdpyinfo's
> > output ?). Anything I can do to make fvwm resolve to 24-bit short of
> > restarting the server with that depth setting explicitly (meaning I'd
> > have to call the powers that be to change the configuration on this
> > machine - after a million+1 questions) ? What do other window managers
> > (like CDE) do to resolve this ?
>
> If you start fvwm without -visual{Id} it asks the server for the
> default visual and use it (I do not think that fvwm is broken here; it
> does not grep xdpyinfo, it uses the X library).
In fact I do not know what we should do with a card with 2 depths
for a given visual. I found nothing in the X lib (or in the Xevi
extension) for such a situation. I imagine that there is an X extension
to deal with this situation and we should use it to choose the desired
depth.
Olivier
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Thu Oct 03 2002 - 12:46:21 BST