NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

GUI Bug?

In TS, when editing the IVI Tools field for a set (&get) attribute, the Attr Name and Value fields do not always (OK, seldom) take, and require the user to type eroneous characters (ie:'"')at the end of the GUI box 1st, then delete them.

Not sure if you have seen this?

rjmiller
0 Kudos
Message 1 of 5
(3,266 Views)
rjmiller -
What version of TestStand are you using?

Scott Richardson (NI)
Scott Richardson
https://testeract.com
0 Kudos
Message 2 of 5
(3,266 Views)
Version 3.0.

A little more information that I have. The problem seems to exist when 100% mouse clicking choices to fill in the fields.

For example, I have some global data structures containing the IVI ATTRIBUTE numbers, with either SEQ file parameters or global data for the IVI string/number fields I'm filling in. When I select the global (or parametric) data, using the mouse to fill the desired fields, the data is pasted correctly but when I click "OK" in the IVI box then check to see if it took by re-editing the IVI step, it didn't. I have to actually type something in the field after selecting the global/parametric data, then delete it, leaving the original mouse selected data.

Hard to explain GUI interaction, I'm sorry.

rjmiller
0 Kudos
Message 3 of 5
(3,266 Views)
RJMiller -
There is a problem in the expression edit control that the IVI step types use that caused this problem. When the code was rewritten to use the new TestStand 3.0 UI Expression Edit control, some of the VB code that commits the changes made to the text box using the browse control was not correct. This should be fixed in the next release.

Here is a recompile of the TsIviStep.dll that should fix the problem.
You can replace the copy under \Components\NI\StepTypes\IviSteps\ on your developement system to use it. You must restart the sequence editor. You do not need to distribute this DLL with a test system unless the test system will be editing steps.

Please let me know if you see any additional issues wit
h the fix DLL.

Scott Richardson (NI)
Scott Richardson
https://testeract.com
0 Kudos
Message 4 of 5
(3,266 Views)
Thanks, this fixed the problem.

rjmiller
0 Kudos
Message 5 of 5
(3,266 Views)