Re: two display devices?
- From: "Bruce Eitman \(eMVP\)" <beitman.nospam@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 9 Jun 2006 10:47:27 -0400
I beleive what Richard meant was that the apps need to know the display
coordinates. So when you use the APIs, you will set the window coordinates
to the apprpriate display. So if you have two displays that are 100 display
units wide and high (not real world but the math is easy) one would be from
(0,0) to (99, 99) and the other would be from (100, 0) to ( 199, 99) and the
virtual display would be from (0,0) to (100,99)
--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net
Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member
<mailto635@xxxxxxxxx> wrote in message
news:1149826285.182999.99890@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Richard,
Thanks for your inputs.
One solution, used more than once, is to present the two adaptors to GWESNormally applications use GWES API such as CreateWindowEx, rather than
as
a single device, with the second adaptor acting as an extended display
surface.
At the app level, you need to know the areas of the display surfaces
corresponding to adaptor 1 and 2.
using the display surfaces directly. If so, how can this be done?
I think two display devices can be exposed through two different
display drivers.
Then the applications should be able to use EnumDisplayDevices and
then CreateDC for a particular device.
After that, is there any possibility for the application to create a
window on a particular device? For ex: App1 wants to create its window
on the display1 and app2 wants to create its window on the display2.
regards
.
- References:
- two display devices?
- From: mailto635
- Re: two display devices?
- From: Richard Lee eMVP
- Re: two display devices?
- From: mailto635
- two display devices?
- Prev by Date: Re: PB 5.0: Image only boots 99%
- Next by Date: Re: Windows Mobile OAL development problem
- Previous by thread: Re: two display devices?
- Next by thread: Re: What is "Code space full, fixing up <XYZ.dll> to ram space" ?
- Index(es):
Relevant Pages
|