David -- ............................................................................. David L. Thompson Visualization and Imagery Solutions, Inc. mailto:[EMAIL PROTECTED] 5515 Skyway Drive, Missoula, MT 59804 Phone : (406)257-8530
Jeff and I have been looking at the DX internals lately due to a
project we're considering and was wondering if anyone might have a
unique solution. Currently, DX shares a named X-Window between the
executive and other processes such as the VPE to perform visual
displays. It's quite unique and I can't see a solution for a Windows
equivalent. For example, the VPE creates an Image Window (X-Window
internally) and then passes this X-Window's name via communication to
the executive. The exec can then set procs as well as use this window
as its own thus having two applications manipulate the same window.
Within Win32, it is possible to share a common window via a handle,
but you don't have this same advanced functionality of being able to
assign the window's events to two different programs. So if I were to
try and design a Windows native version of DX, how might this
functionality be handled--remember, this graphic window can also be
OpenGL based. We've thought of making the executive an ActiveX
control but not totally sold on this idea. Any suggestions welcome.
- [opendx-dev] Ideas for X independency David Thompson
- Re: [opendx-dev] Ideas for X independency Gregory D Abram
- Re: [opendx-dev] Ideas for X independency David Thompson
- Re: [opendx-dev] Ideas for X independency Richard Gillilan
- Re: [opendx-dev] Ideas for X independency Gregory D Abram
