is it safe to use one sequence view control for both sequence file view and execution view

[kwkengineer]

I've got a Teststand user interface written in Labview 2012.  It has a single Sequence View control, and I use the ConnectSequenceView method to switch between just viewing the loaded sequence file and the running execution.  Let me restate.  When a sequence file is running, the control is connected to the Execution manager.  Otherwise it is connected to the sequenceFileView manager. 

I'm begining to suspect that I have issues related to this control when I do the following.

1. Load a sequence file

2. Execute Single Pass

3. Execution completes

4. Unload and Release sequence file

5. Load a different sequence file

6. Execute single pass

7. Labview crashes

Am I missing a step?

Thanks,

Kevin

[~jiggawax~]

Just a thought-

I would have 2 if I were you.  Dedicated to their respective manager controls.

Then I would use a invisible tab control and just switch the tab control depending on if an execution is happening or not.  To the user they wouldn't know the difference.  That way they are always populated with the correct things.

My 2 cents though.

[kwkengineer]

The reason we don't is because we already have the hidden tab control to switch between sequential and parallel views.  So each of those views have their own controls. 

To your point I could just put another tab in the tab.

[~jiggawax~]

The full featured UI that ships with TestStand hanldes both sequential and parallel with the same controls.  Is there a reason you don't want that?

Plus they use the Tab method to switch between edit and execution.

Cheers,

[~jiggawax~]

My bad it doesn't tile like the sequence editor does.  I forgot.

[kwkengineer · Accepted solution]

So it would seem the Labview crash I mentioned in the original post is unrelated to the the mixed use of the sequence view control.  However during my troubleshooting I did notice I was missing the step of disconnecting one view from the control prior to connecting the other view. 

And for the record I think there are a lot of things wrong with the architecture used in the full-featured example, but it also has too many features for what we need.  Just need the simple "press a button", and "run a test" for the operators.  Everybody else uses the Sequence Editor.

All is well.  Thanks for the input.

Kevin