Am 02.10.2010 15:29, schrieb Jacek Caban:
+typedef enum D3D10_SRV_DIMENSION1 +{ + D3D10_1_SRV_DIMENSION_UNKNOWN = 0, ... + D3D10_1_SRV_DIMENSION_TEXTURECUBE = 9, + D3D10_1_SRV_DIMENSION_TEXTURECUBEARRAY = 10 +} D3D10_SRV_DIMENSION1;
You probably might add those to d3dcommon.h and only add a typedef. It was changed in one of the sdks.
Cheers Rico
On 10/3/10 5:44 PM, Rico Schüller wrote:
Am 02.10.2010 15:29, schrieb Jacek Caban:
+typedef enum D3D10_SRV_DIMENSION1 +{
- D3D10_1_SRV_DIMENSION_UNKNOWN = 0,
...
- D3D10_1_SRV_DIMENSION_TEXTURECUBE = 9,
- D3D10_1_SRV_DIMENSION_TEXTURECUBEARRAY = 10
+} D3D10_SRV_DIMENSION1;
You probably might add those to d3dcommon.h and only add a typedef. It was changed in one of the sdks.
This can't work for enums. Note that there are D3D10_1_* value names, not only types.
Jacek
Am 04.10.2010 18:35, schrieb Jacek Caban:
On 10/3/10 5:44 PM, Rico Schüller wrote:
Am 02.10.2010 15:29, schrieb Jacek Caban:
+typedef enum D3D10_SRV_DIMENSION1 +{
- D3D10_1_SRV_DIMENSION_UNKNOWN = 0,
...
- D3D10_1_SRV_DIMENSION_TEXTURECUBE = 9,
- D3D10_1_SRV_DIMENSION_TEXTURECUBEARRAY = 10
+} D3D10_SRV_DIMENSION1;
You probably might add those to d3dcommon.h and only add a typedef. It was changed in one of the sdks.
This can't work for enums. Note that there are D3D10_1_* value names, not only types.
Yeah sure, you need to add it as enums. See e.g. http://msdn.microsoft.com/en-us/library/ff728736%28VS.85%29.aspx .
I'm not sure if this could be a problem, but if you include only d3d11.h which includes d3dcommon.h and you use e.g. D3D10_1_SRV_DIMENSION_TEXTURECUBE a build against our headers might fail because D3D10_1_SRV_DIMENSION_TEXTURECUBE is not defined (what a bad example). Well written apps would of course use D3D11_SRV_DIMENSION_TEXTURECUBE or D3D_SRV_DIMENSION_TEXTURECUBE in that case.
Note: This is mostly the same for the current d3d10.h, but the stuff was moved to d3dcommon after our d3d10.h was in!
Cheers Rico