QUOTE (ragglefrock @ Jul 28 2008, 05:31 PM)
You could affect the order based on where you click on the accepting wire (eg: if you click on the top of it then your wire will first, if you click on the bottom of it your wire will be last). This is the same concept that currently exists in LabVIEW when you right-click on a wire and "insert" a primitive. If the primitive has 2 inputs, then the existing wire will be in a different input depending on when you originally right-clicked. That's not a great explination - let me know if that's not clear.
QUOTE (ragglefrock @ Jul 28 2008, 02:11 PM)
There's a really cool feature with Dynamic Data Type that allows you to merge signals really easily on the block diagram. Ignoring the fact that I never actually use DDT...
Is the reason that you don't use it because you don't like it or because it's not available where you would want to use it? Personally, I'm in the camp of the former - the LabVEW IDE doesn't know what sort of crazy thing I'm trying to acheive, so don't automatically insert anything. For example, if I have two controls, and one of them is wired to an indicator: let's say I want the other one to got to the indicator - I usually just wire it in and then delete the (now broken) wire from the previous control (this is particulatily important when you've spent time on laying out your wires). I would not want LabVIEW to put a bundle array or build cluster in there (partly because that would mean that I'd also need to change my indicator). You ight think that the error cluster is different, and you would always want to merge errors, but that isn't always the case. IMHO, DDT is a great method for making entry into LabVIEW easier for the lab guy who just wants to get his new M-series and SCB-68 up and running, but I don't want to see it pervade any more than that.