NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

MessagePopup Active Control on Response String in 3.5

I recently upgraded from teststand 3.1 to 3.5. My testsequence uses Message Popups with the active control on an initial response string.
In teststand 3.1 the string is selected, so the user will erase the string when typing into the text box.
In teststand 3.5 the text box is active but the text is not selected, so the user will type in front of the initial response string.
Is it possible to make the string selected in teststand 3.5?
0 Kudos
Message 1 of 5
(3,368 Views)

Hi,

Its possible a bug has creeped in, as this steptype has changed for 3.5.

A solution would be to clear the Response control in the pre-expression of the step. I think the property is DefaultResponse.

The source code and project files for the step type are available in the NI/Components/StepTypes folder.

Regards

Ray Farmer

Regards
Ray Farmer
0 Kudos
Message 2 of 5
(3,368 Views)

Hi,

I cannot confirm this with 3.1 but certainly with TS3.0 the initial response was highlight when first displayed.

With TS3.5 its not.( Also that you can actual select any text displayed on the panel, bit weird.)

Looking at the code, the Response Control has turned into an ActiveX Control rather than a simple Edit Control.

Also The default responses is held in Step.DefaultResponseExpr.

Regards

Ray Farmer

Regards
Ray Farmer
0 Kudos
Message 3 of 5
(3,353 Views)

Thanks Ray for confirming and investigating this problem.

I have cleared my initial response string in my msgbox (only use one).

I hope NI will soon launch a patch for this. TS 3.5 should be backwards compatible with previous 3.X releases.

We are using other sequences using with more msgboxes, at the moment still running on TS3.1, so we need to check and adapt these sequences before migrating to TS3.5.

Regards

Francis Appels

.
0 Kudos
Message 4 of 5
(3,346 Views)

Francis -
This does appear to be a change of behavior in TestStand 3.5 from TestStand 3.1 and it was not intended. We have logged the issue to be looked at. If we can make something available to address the issue for 3.5, we will let you know via the forum. Thank you for bringing this to our attention.

Scott Richardson
https://testeract.com
0 Kudos
Message 5 of 5
(3,331 Views)