Peeker

QUOTE (normandinf @ May 23 2009, 01:52 PM)

The XY Graph is polymorphic. If you wire a different datatype in a VI, it's gonna change datatype to adapt. But if you use a reference, the datatype needs to be matched to the one in the VI where you got your reference from. Be careful with this because once you've created your reference and used it elsewhere in your program, you have a lot of broken arrows or error pop-ups (if value is a variant) if you ever change the datatype of your graph...

The XY graph reference dilemma has been annoying me as well for a while. I would love to have a general reference to a XY graph so that i dynamically can control what is shown in the graph. Does anyone have a good workaround? Is there a way of up- and down-casting the type so that i can take a more general XY graph reference as input to my sub-vi (or more specifically store the general reference in a parent class)?

My experience is that the SystemExec.vi behaves rather like the windows "run" than like the DOS prompt. Adding cmd.exe before might help, I haven't tried that. Another solution that I have used from time to time is to enter all the commands in a batch (*.bat) file and then calling that file from SystemExec.vi instead. It gets a bit annoying though if you have some sort of dynamic input, then you have to create and save the batch file programatically before running it.

QUOTE (Norm Kirchner @ Jan 21 2009, 02:03 AM)

Ok, so now I put the inplace structure around my array size logic.

http://lavag.org/old_files/monthly_01_2009/post-208-1232497430.png' target="_blank">

Just a reflection:

There is no need to perform Bundle by name on Y at your array size logic. Y is already in the cluster and has not been changed, so this bit could be skipped, hence no memory allocation there.

//Martin