Summary:	Propagate Types
Occurs:	When the Run-time code needs to be generated. When you wire to a terminal. When you call the "Cause Type Propagation" method on the containing VI.
Details:	When mods = 0, a terminal was just wired. When mods = 1, the internal run-time behavior needs to be scripted.
mods = 0:	"This is the routine in which you may update your terminals based on the data types coming into your external node's current input terminals." "termAttrs contains info on the connected controls" "Reply values include: UpdateTerms - This tells LabVIEW you changed the terminal specifications RedoPropTypes - This tells LabVIEW to start the whole proptype process over again. You should probably avoid this one (definitely never return it everytime)." 0x2 - UpdateTerms 0x10 - RedoPropTypes Example: 0x12 = UpdateTerms True, RedoPropTypes True For errOut, specify 0 for noError.
mods = 1:	"This is the routine where you script the run-time behavior of the External Node." extNodeRefNum and C:\Program Files\National Instruments\LabVIEW 7.1\Utility\XNodeSupport.llb\XNodeParts.vi are used in this step. Use the outputs from XNodeParts.vi to dynamically create all the objects and wiring on the internals of the item. This can be one of the trickiest parts, especially if you have a dynamic amount of inputs. Refer to examples when possible, and ensure your code works with a new VI before assuming your code works on the inside of an XNode (you will never *see* this code). For errOut, specify 0 for noError.
mods = default:	Returns 1 - NotImplementedError for errOut currently.