<DUALITY:STRUCT name="MACRO_DWORD_HEX">
<DUALITY:MEMBER name="MACRO_NAME" type="STRING"/>
<DUALITY:MEMBER name="MACRO_VALUE" type="DWORD_HEX"/>
<DUALITY:STRUCT/>
<DUALITY:OBJECT name="WINDOW">
<DUALITY:MEMBER name="DW_STYLE">
<DUALITY:RESTRICT data_type="MACRO_STRING_HEX">
<DUALITY:MACRO_DWORD_HEX MACRO_NAME="WS_EX_ACCEPTFILES" MACRO_VALUE="0x00000010"/>
<DUALITY:MACRO_DWORD_HEX MACRO_NAME="WS_EX_APPWINDOW" MACRO_VALUE="0x00040000"/>
<DUALITY:MACRO_DWORD_HEX MACRO_NAME="WS_EX_CLIENTEDGE" MACRO_VALUE="0x00000200"/>
<DUALITY:MACRO_DWORD_HEX MACRO_NAME="WS_EX_COMPOSITED" MACRO_VALUE="0x02000000"/>
<DUALITY:RESTRICT/>
<DUALITY:MEMBER/>
<DUALITY:OBJECT/>
<DUALITY:OBJECT name="RC11" module_type="MODULE_RC" >
<DUALITY:MEMBER name="WINDOW:APP" type="WINDOW"/>
</DBXML:OBJECT>
Data Binding XML to Object Models
If I'm Data Binding XML to an Object Model is the model most obviously represented in XML?
eg.
Model:
Would it be better to just create a model through the use of structures and enumerations? Or other? Is the above overly complex or simple?
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement