nanogui@linuxhacker.org

In the past, we had touched on the subject of supporting
multiple screen/mouse/keyboard devices with Microwindows.  I
am now to the point in my project where I need to come up with
a solution.  The main issue is that I am working with VxWorks,
a thread-based operating system with a shared global name-space.
So, as opposed to Linux/Windows/OS-9/QNX/etc where one could
just fork off multiple processes each with their own independent
version of Microwindows running, I need to configure Microwindows
to support multiple screens using the same global name-space.

I've discovered that there are many global variable used by
Microwindows.  Some of these are basically constants (eg,
standard palettes, fonts, and mwSYSMETRICS_xxx).  Others are
actively used for the processing of window/cursor/clipping
calls.  It is these globals that I propose putting either into
the HCD device context structure (for the mwin globals) or
into the PSD screen device structure (for the engine globals).

I am in the process of starting the implementation of this
proposal and will provide additional details after everything
is working.  But are there any comments on why this is needed
or variations on accommodating multiple screens?

BAT
-- 
Brent A. Thompson, Next Level Communications <www.nlc.com>
1776 22nd Street #100, West Des Moines, IA 50266-1444
EMail: <Thompson@nlc.com>, Phone: (515)991-3853