Can someone explain why using a LabVIEWIOControl variable to maintain the DAQmx Task Name from Labview causes the sequence editor to become extremely slow. The attached vi is doing nothing more than opening a chan (analog output) on a pxi-6723 and closing it via setting of OPERATION enum (see teststand sequence).
To simulate the problem, right click on Action Step and select "specify module". Once the "module" tab is open, click back and forth between Action 1 and Action 2 (1,2,1,2,1..etc). You should see quite a delay pulling up the step module info going from 2 back to 1.
My "actual" application runs fine but editing a step can take 10 secs to pull the module info. Note: This is the only variable type which causes this problem i.e. I've used cluster arrays, string, enums..ect without problems in the past.
I've attached a teststand seq which calls the vi.
