This was to support polymorphism for Custom data type, similar to how you define a polymorphic port "siICENodeDataLong | siICENodeDataFloat" with built-in data types.
For custom types, you can pass in an array of custom types that the port accepts. From: [email protected] [mailto:[email protected]] On Behalf Of Steven Caron Sent: Friday, April 12, 2013 11:43 AM To: [email protected] Subject: Re: C++ : custom ice node with custom data type hey ho chung thanks for the response! i am well aware of this example code and have been referencing it already, my question still stands. if you look at the example at line 118-124 CStringArray outStateCustomType(1); outStateCustomType[0] = L"GridWalkState_v1"; st = nodeDef.AddOutputPort(ID_OUT_OutState, outStateCustomType, siICENodeStructureSingle, siICENodeContextComponent0D, L"Out State",L"OutState", ID_UNDEF,ID_UNDEF,ID_CTXT_CNS); why is it a string array? why not just a single CString? can i put two data types into one output port? doesn't make sense. i am trying to understand if there is some trick or benefit for having the argument be an array of strings vs a single string s On Thu, Apr 11, 2013 at 8:07 PM, Ho Chung Nguyen <[email protected]<mailto:[email protected]>> wrote: You can connect to the SDK example workgroup and check out this custom ICE node <InstallationPath>\XSISDK\examples\workgroup\Addons\CustomICENodes\cppsrc_gridwalker\GridWalker.cpp
<<attachment: winmail.dat>>
