Post

 Resources 

Console


RE: The return to VB... DX7 (D3D IM) Marek Mikulec (2 replies, 0 views) (2000-Jun-23)
-
Adam, Thanks very much for the info, more about question 1 then: "...however the two are not compatible with each other when it comes down to the actual objects, i.e you couldn't pass DirectDrawSurface7 object to a c++ function expecting an IDirectDrawSurface7 type, since M$ in there infinite wisdom, wrapped up the objects, whereas all previous versions of DX support in VB (curtesy of Patrice Scribe) where type libraries. So anyway, porting between VB and C++ is as simple as Cut/Paste/Modify really..." Actual objects, or that is, data being identical, is the problem. You see, there are 2 main apps I'm going to develop: 1) Configuration application 2) Mission/script builder In both cases, but defenitely in #1, I'm going to need to enumerate the computer entirely, let the user select modes, LODs, customise options, and then save all of this enumeration info, (drivers, modes, texture formats, depth + vertex buffer capabilities, dsound caps... you get the point) into a file in which the 3D Engine (being developed in VC++) will be able to use. So, my main concern is that the object data (flag, caps, etc) is identical and most imperitively, the SAME size in bytes. Do you know if it is? If you're not sure, does VB have a sizeof() operator I could use with my own experiments? Thanks for your help, Marek


-
Up One Level | Back to Forum

RE: The return to VB... DX7 (D3D IM) Jack Hoxley (1 reply) (2000-Jun-23)
RE: The return to VB... DX7 (D3D IM) Marek Mikulec (0 replies) (2000-Jun-24)

Copyright © 2002 - 2004 Eric Coleman, Peter Kuchnio , et. al.
There have been 105 visitors within the last 20 minutes
RSS News Feed