Unable to change step settings

[CoastalLabVIEWER]

I'm having an odd problem with 4.5.1 where I am inevitably doing something that is locking the step settings from being changed.  It seems to be related to calling by expression but I've been unable to nail down what is causing it.  The parameters go from having a white background and are able to be changed to having a different background and the parameters can't be changed.  I attached a pic.  Am I just doing something dumb or what?

[dug9000]

Are you perhaps running an execution which uses that sequence file? You can't edit a sequence file while it's in use by an execution.

Hope this helps,

-Doug

[LabBEAN]

Seen the same thing with TestStand 2010 SP1.  Seems to happen randomly.  The only recourse so far:  restart TestStand or restart PC.  (I work with SmokeMonster, so maybe it has something to do with our custom process model, although the symptom is intermittent.)

[dug9000]

When it happens again, I recommend checking the caption of the sequence editor (if you are running in the sequence editor) to see if any executions are still running. You might have hidden executions which are still using the file.

-Doug

[Rand_H]

Hello all.

Sorry to bump this old post. We are having this same problem from updating to TS2010.

Randomly (even from fresh open with no executions) we can no edit step settings. I have only seen this in the module tab. Properties tab is working fine.

It seems like this tab is "logged out". Restarting TS fix the problem always.

Any idea?

[Erik_Crank]

The original post shows an image of the Module tab for a sequence call step. It appears that only the parameters control is read-only; the File Pathname and Sequence controls appear editable. Can you confirm that this problem occurs only with the parameters control on the Module tab for sequence call steps?

Although we could not reproduce this problem we did make some changes to the sequence call module tab for TestStand 2012 that should prevent this problem from occurring.

[CoastalLabVIEWER]

It has been awhile since we have had this problem but I seem to recall VI calls were also affected, not sure about other step types we used like (sequences and VIs are the bulk of it).  We haven't seen the problem in awhile because we've moved out of a phase where we were doing a lot of development and changing sequences around a lot.  It seemed to be most prevalent when we were changing things, either deleting and creating new sequences or adding/removing parameters, that were being called by other sequences in other .seq files.  I'd like to say we've only seen it happen once or twice in the past 6 months or so.  If we see it again (before we upgrades to 2012) I'll try to get some more screenshots of different step types.

[Rand_H]

Hello,

I think I catch the trigger of the problem. Please see attached sequences to try to reproduce it.

Only 2 sequences, first calls second. Then we add a lot of parameters in this second. After this you will see the typical red blincking icon informing about prototype change.

Instead of clicking if you change the focus from this changed call to a normal call and return you will see this "lock" of the module tab.

Let's see if you can reproduce it!