How to use DirectX without Windows Mobile

[Frankie D.]

I have a custom CE image based on x86. DirectX component has been added in
Platform Builder, and a reference to WindowMobile.DirectX component in VS.
InvalidDeviceException is thrown while construction the Device object.

presentParams.Windowed = true;
presentParams.SwapEffect = SwapEffect.Discard;

device = new Device(
0,
DeviceType.Default,
this,

CreateFlags.None, presentParams);

DirectX can be used only in WindowsMobile environment? What should be added
in Platform Builder?

Please help,

Thanks in advance,

Frankie

 

[Carsten Unterberg]

Hi Frankie,

I do not think that it is possible to use WindowsMobile.DirectX under a
"plain" Windows Ce image. WindowsMobile is a subset of several Windows
Ce-components. WindowsMobile need nearly all components for
gui/graphical-stuff from Windows Ce. WindowsMobile.DirectX need these
components to run. It is also possible that WindowsMobile.DirectX asks for
the current OS Name and such information.

Best regards,

Carsten Unterberg | Test-Framework
http://test-framework.blogspot.com/

 

[Carsten Unterberg]

Hi Frankie,

I do not think that it is possible to use WindowsMobile.DirectX under a
"plain" Windows Ce image. WindowsMobile is a subset of several Windows
Ce-components. WindowsMobile need nearly all components for
gui/graphical-stuff from Windows Ce. WindowsMobile.DirectX need these
components to run. It is also possible that WindowsMobile.DirectX asks for
the current OS Name and such information.

Best regards,

Carsten Unterberg | Test-Framework
http://test-framework.blogspot.com/

 

[Frankie D.]

Hi,

Thank you for your answer.

Is there any way to use DirectX3d in CF?

Why contains CF WindowsMobile.DirectX if can not be used?

WindowsMobile.DirectX is a component declared in CF and implemented in WM,
isn't it?

It follows that WM is not a real subset, isn't it?

Best regards,

Frankie

 

[Frankie D.]

Hi,

Thank you for your answer.

Is there any way to use DirectX3d in CF?

Why contains CF WindowsMobile.DirectX if can not be used?

WindowsMobile.DirectX is a component declared in CF and implemented in WM,
isn't it?

It follows that WM is not a real subset, isn't it?

Best regards,

Frankie

 

[Chris Tacke, eMVP]

The CF contains the WindowsMobile.DirectX namespace for use in Windows
Mobile devices. The namespace is what we would call a "clue". It doesn't
say System.DirectX or WindowsCE.DirectX.

Can D3DM be used in CE from managed code? I've not done it, but I'm highly
inclined to say "yes" since there are very few things you can't do with
P/Invoke. There just isn't a CF-supplied wrapper for it.

As to why that is, my guess is that the WinMo D3DM has more in it than the
version in CE, plus it predates the CE version. It would have been more
work to make it work under CE, meaning more test and more implementation
time, and the reality is that I've not seen any non WinMo device that
supported it (in fact most WinMo devices don't support it well either).

The entire point here is that you're not going to be using D3DM (not without
a lot of work anyway), so instead of fixating on the reasoning behind that,
you should describe the actual problem you're trying to solve. We can then
provide you with suggestions on how to go about solving that problem.


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com

 

[Chris Tacke, eMVP]

The CF contains the WindowsMobile.DirectX namespace for use in Windows
Mobile devices. The namespace is what we would call a "clue". It doesn't
say System.DirectX or WindowsCE.DirectX.

Can D3DM be used in CE from managed code? I've not done it, but I'm highly
inclined to say "yes" since there are very few things you can't do with
P/Invoke. There just isn't a CF-supplied wrapper for it.

As to why that is, my guess is that the WinMo D3DM has more in it than the
version in CE, plus it predates the CE version. It would have been more
work to make it work under CE, meaning more test and more implementation
time, and the reality is that I've not seen any non WinMo device that
supported it (in fact most WinMo devices don't support it well either).

The entire point here is that you're not going to be using D3DM (not without
a lot of work anyway), so instead of fixating on the reasoning behind that,
you should describe the actual problem you're trying to solve. We can then
provide you with suggestions on how to go about solving that problem.


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com