Limiting X-Manager to 16-bit colour [3]

Hi,

Is there any way of restricting the reported display depth
of X-clients run under X-Manager to 16-bit?, currently it seems
to always report it's colour depth as 24-bit when using the
TrueColor modes.

I've got my Windows machine running in 16-bit as well, but
X-Manager seems to ignore this...

Many thanks,
Richard

Xmanager uses 24-bit colors instead of 16-bit colors to simplify the color handling of X applications. 24-bit colors are properly converted to 16-bit colors and most X applications don't have a problem.

If you have a specific need for the true 16-bit colors, please let us know it. We will consider it for our future version.

Thank you for your feedback.

- Technical Support

> If you have a specific need for the true 16-bit colors,
> please let us know it.

We are currently making use of a graphics library called GGI,
it effectively emulates a frame buffer device in either a real
framebuffer (like SVGAlib) or in an X-window.

As part of this the library allows direct access to the screen
buffer memory. For speed, we've been writing our application to
use the screen buffer in 16-bit mode only (as we single task
on our destination platform).

It's a bit of an unusual case though, and we can probably work
around it (by just rewriting our debugging graphics routines
to run in all bit-depths) but still - it's one for the wish-list!

Many Thanks,
Richard

Thank you for your feedback.

Even though Xmanager supports 16-bit color visual, the RGB bits might be different with your target device. And Windows color schemes are a little bit tricky and it's really difficult to support perfect 16-bit visual.

Expaning 16-bit to 24-bit is more easier than sqeezing 24-bit pixels to 16-bit one.

We think that emulating a frame buffer for X window server is not an easy task. It might cause many side effects on some X servers. At the first stage, using 24-bit frame buffer is more safe method.

We hope this could help you.

- Technical Support