"Søe" <Se@discussions.microsoft.com> wrote in message
news:1CB53741-1636-493D-80C8-E95CEC884AD9@microsoft.com...
> Dear Kevin,
>
> I'm very sorry but I don't quite follow you (where to look)!
>
> My problem is that I have a form, and now I would like to create a
> Direct3D
> device, like this:
>
> m_Device = new Dvice(adapter, ......)
>
> How do I determine the adapter the form i running on?
> (Ps. I can't use the device constructor that takes an IntPtr, since I
> can't
> set the Presentationparams)
>
>
> --
> Kindly regards (and please advice if possible)
> Jens Søe Christiansen
>
>
> "Kevin Spencer" wrote:
>
>> See:
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/directx9_c/DirectX_9_Frequently_Asked_Questions.asp
>>
>> The Device is a class that encapsulates access to a display adapter. When
>> you work with a Device, you are working with a graphics adapter. The FAQ
>> listed above will tell you how to get the various characteristics of the
>> various adapters on your system.
>>
>> --
>> HTH,
>>
>> Kevin Spencer
>> Microsoft MVP
>> Professional Chicken Magician
>>
>> A man, a plan, a canal.
>> a palindrome that has gone to s**t.
>>
>>
>> "Søe" <Se@discussions.microsoft.com> wrote in message
>> news:0C6F7BB2-31C8-4F52-8388-4EF56CC3A381@microsoft.com...
>> > Dear Kevin,
>> >
>> > I know about the Direct3D. My application is blending and mixing
>> > textures
>> > and everything, but I still can't seem to figure out on which display
>> > adapter
>> > m form is running, in a multi-dispay environment (specially when the
>> > primary
>> > display is to the right)!
>> >
>> > --
>> > With regards
>> > Jens Søe Christiansen
>> >
>> >
>> > "Kevin Spencer" wrote:
>> >
>> >> The Device class is part of the Direct3D namespace, which is included
>> >> in
>> >> the
>> >> SDK, along with all the documentation.
>> >>
>> >> --
>> >> HTH,
>> >>
>> >> Kevin Spencer
>> >> Microsoft MVP
>> >> Professional Chicken Magician
>> >>
>> >> A man, a plan, a canal.
>> >> a palindrome that has gone to s**t.
>> >>
>> >>
>> >> "Søe" <Se@discussions.microsoft.com> wrote in message
>> >> news:6F3E455F-1005-48D3-9057-C8248E11ABF3@microsoft.com...
>> >> > hmmmm hi Kevin,
>> >> >
>> >> > I'm very sorry but I can't seem to find anything that actually could
>> >> > help
>> >> > me!
>> >> >
>> >> > --
>> >> > With regards
>> >> > Jens Søe Christiansen
>> >> >
>> >> >
>> >> > "Kevin Spencer" wrote:
>> >> >
>> >> >> Microsoft.DirectX.Direct3D.Device
>> >> >>
>> >> >> You need the DirectX SDK installed to use it. See
>> >> >> http://msdn.microsoft.com/directx/sdk/
>> >> >> --
>> >> >> HTH,
>> >> >>
>> >> >> Kevin Spencer
>> >> >> Microsoft MVP
>> >> >> Professional Chicken Magician
>> >> >>
>> >> >> A man, a plan, a canal.
>> >> >> a palindrome that has gone to s**t.
>> >> >>
>> >> >>
>> >> >> "Søe" <Se@discussions.microsoft.com> wrote in message
>> >> >> news:7518332A-3E83-4A54-8C5E-A8D48018B5A5@microsoft.com...
>> >> >> > Dar Kevin,
>> >> >> >
>> >> >> > I'm very sorry for my stupidity, but I don't seem to have a
>> >> >> > device
>> >> >> > class
>> >> >> > in
>> >> >> > the Device, running manage C# .Net 2.0?
>> >> >> >
>> >> >> > Please advice if possible, since this is very crucial for us.
>> >> >> >
>> >> >> > --
>> >> >> > Kindly regards
>> >> >> > Jens Søe Christiansen
>> >> >> >
>> >> >> >
>> >> >> > "Kevin Spencer" wrote:
>> >> >> >
>> >> >> >> Ah, this is a DirectX question?
>> >> >> >>
>> >> >> >> Is this managed DirectX or native? If managed, use the
>> >> >> >> Device.Device
>> >> >> >> class.
>> >> >> >>
>> >> >> >> --
>> >> >> >> HTH,
>> >> >> >>
>> >> >> >> Kevin Spencer
>> >> >> >> Microsoft MVP
>> >> >> >> Professional Chicken Magician
>> >> >> >>
>> >> >> >> A man, a plan, a canal.
>> >> >> >> a palindrome that has gone to s**t.
>> >> >> >>
>> >> >> >>
>> >> >> >> "Søe" <Se@discussions.microsoft.com> wrote in message
>> >> >> >> news:29CBB352-C849-4FF3-BA2D-5E233082D910@microsoft.com...
>> >> >> >> > Hi Kevin,
>> >> >> >> >
>> >> >> >> > how should GetWorkingArea help me figure out the display
>> >> >> >> > adapter
>> >> >> >> > th
>> >> >> >> > form
>> >> >> >> > is
>> >> >> >> > running on?
>> >> >> >> >
>> >> >> >> > --
>> >> >> >> > With regards
>> >> >> >> > Jens Søe Christiansen
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > "Kevin Spencer" wrote:
>> >> >> >> >
>> >> >> >> >> Use the Screen.GetWorkingArea method.
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> HTH,
>> >> >> >> >>
>> >> >> >> >> Kevin Spencer
>> >> >> >> >> Microsoft MVP
>> >> >> >> >> Professional Chicken Magician
>> >> >> >> >>
>> >> >> >> >> A man, a plan, a canal.
>> >> >> >> >> a palindrome that has gone to s**t.
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> "Søe" <Se@discussions.microsoft.com> wrote in message
>> >> >> >> >> news:E54D9BA5-D499-40FF-ADC0-55D7206DD0DC@microsoft.com...
>> >> >> >> >> > Hi,
>> >> >> >> >> >
>> >> >> >> >> > I'm trying to create an project running in a dual display
>> >> >> >> >> > environment.
>> >> >> >> >> > My
>> >> >> >> >> > application instantiate a Windows Form on each monitor, and
>> >> >> >> >> > that
>> >> >> >> >> > works
>> >> >> >> >> > great.
>> >> >> >> >> > However, I need to use DirectX and thereby I need to figure
>> >> >> >> >> > out,
>> >> >> >> >> > which
>> >> >> >> >> > display adapter the form is running on. Until now that
>> >> >> >> >> > hasn't
>> >> >> >> >> > been
>> >> >> >> >> > easy! I
>> >> >> >> >> > tried using the Screen class, but if the primary window is
>> >> >> >> >> > to
>> >> >> >> >> > the
>> >> >> >> >> > right,
>> >> >> >> >> > then
>> >> >> >> >> > the first screen in Screen.AllScreens is the one on the
>> >> >> >> >> > left,
>> >> >> >> >> > and
>> >> >> >> >> > so
>> >> >> >> >> > I
>> >> >> >> >> > can't
>> >> >> >> >> > just use the index in Screen.AllScreens.
>> >> >> >> >> >
>> >> >> >> >> > Could anyone please help me figure out how to determine the
>> >> >> >> >> > adapter
>> >> >> >> >> > a
>> >> >> >> >> > form
>> >> >> >> >> > is running on?
>> >> >> >> >> >
>> >> >> >> >> > Kindly regards
>> >> >> >> >> >
>> >> >> >> >> > --
>> >> >> >> >> > Jens Søe Christiansen
>> >> >> >> >> >
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>