| Bug ID | Fixed Issue |
| Sequence Editor |
| 4ARE473S | Fixed an issue where TestStand execution speed slowed drastically as you added expressions to the Watch View pane. You can also hide the Watch View pane to improve the TestStand execution speed. |
| 49HCFAI0 | Fixed an issue where the Types window generated an error when the file you selected contained a type with an empty name. |
| 4D47OHAG | Fixed an issue where the sequence editor crashed when displaying an expression that called the InsertElements function. |
| 4A4F6HZL | Fixed an issue where the .NET Module tab generated an error when you selected a property that required parameters. |
| 4D6GKPRA | Fixed an issue where the .NET Module tab failed to release a reference to an assembly, which prevented you from rebuilding the assembly. |
| 4DJAKLUV | Fixed an issue where the sequence editor hung when you resized a panel horizontally to hide or fully expand the panel. |
| 4DQAUJRA | Fixed an issue where the sequence editor hung when you pressed "*" to expand RunState in the Variables and Watch View panes. |
| 4DRFH0UZ | Fixed an issue where the Variables pane crashed when RunState.InitialSelection.SelectedPropertyObjects contained a reference to a SequenceContext object. |
| UI Controls |
| 49F9SHZL | Fixed an issue where the text in a Button UI control stopped at the edge of the button instead of wrapping to a new line. |
| 4D5H5200 | Fixed an issue where the Listbox UI control generated an error when you moved the mouse over the area to the right of the last column. |
| 4BQGQ8B8 | Fixed an issue where the VariablesView control incorrectly cleared the SelectedPropertyObjects collection. |
| LabVIEW |
| 4ADBQ500 | Fixed an issue where the LabVIEW Module tab generated an error when you used a relative path to browse to and select an Express VI. |
| 48MD0500 | Fixed an issue where TestStand could not configure some Express VIs using LabVIEW 8.5. |
| 4D4A2500 | Fixed an issue where the LabVIEW Module tab displayed a blurry VI context help description. |
| 492BJ800 | Fixed an issue where the LabVIEW Adapter truncated error messages that contained "ProxyCaller" in the error text. |
| 47FERQ77 | LabVIEW 8.5 fixed an issue where top-level menus were disabled after you clicked other top-level menus. |
| 3TN8DD00 | LabVIEW 8.5 fixed an issue where TestStand hung when calling a remote VI that called a LabVIEW-built DLL. |
| 4D98S9UZ | Fixed an issue where a module call to a VI returned an error when executed in a LabVIEW user interface using the LabVIEW Run-Time Engine and the called VI and the user interface used different versions of the same subVI. |
| 4BMAB7ZL | Fixed an issue where TestStand XML and binary files did not save the Is Binary String setting from the LabVIEW Cluster Passing tab of the Type Properties dialog box. |
| LabWindows/CVI |
| 493BENB8 | Fixed an issue where the LabWindows/CVI Adapter prematurely unloaded a module DLL when the adapter could not find a function in the module. |
| 4DGA12IA | Fixed an issue where a LabWindows/CVI user interface displayed an invalid handle error every time you switched between the Executions and Sequence Files panels of the List Bar control and you previously cancelled a shutdown operation. |
| Miscellaneous |
| 48GG5NB8 | Fixed an issue where TestStand 3.1 and later did not set the status of a Sequence Call step to "Terminated" when a termination occurred while executing the steps in the called sequence. |
| 4D6DSOJO | Fixed an issue where the .NET Adapter generated an error when a step tried to store a .NET reference as an element of an array of reference objects. |
| 48JBKBG0 | Fixed an issue where TestStand failed to disconnect switching routes with sequence lifetimes after a Property Loader step imported values to the sequence and you disabled the Import to Run-time Sequence Only option on the Properties tab of the Edit Property Loader dialog box. |
| 4AEE6UIF | Fixed an issue where TestStand incorrectly handled /r and /n characters in string properties when saving and opening files. |
| 45PDPEJ6 | Fixed an issue where the Microsoft Visual Basic 6.0 runtime corrupted memory when TestStand reloaded a Visual Basic ActiveX component. This typically occurred when TestStand tried to display an array result in a graph in an HTML or XML report and the execution ran steps using the LabVIEW Run-Time Engine. |
| 496F4URA | Fixed an issue where the ActiveX Adapter did not pass the default value for a parameter when you configured the step with the TestStand 4.0 Sequence Editor. |
| 4D3BO6B8 | Fixed an issue where the default value of the Engine.OutputMessagesEnabled property was True instead of False, which allowed TestStand to collect output messages for user interfaces that did not process the messages. |
| 4D59ABB8 | Fixed an issue where the Auto Schedule step did not exit its block when you set the Use Auto Scheduled Resource step run mode to Skip. |
| 4CTL1300 | Fixed an issue where the remote server a Call Executable step uses crashed when trying to log calls. |
| 4CMGR3IF | Fixed an issue where the sequence file XML schema did not include a LabVIEW cluster passing attribute. |
| 4BUA5700 | Fixed an issue where TestStand did not display an ATML report because it incorrectly generated the ATML report when the results contained a container array. |
| 4BUA5000 | Fixed an issue where the ATML report did not correctly display limit data and error text. |
| 4D3DL1RA | Fixed an issue where editing the numeric format of a type property did not mark all files that use the type as modified. |
| 4CTFKU00 | Fixed an issue where the horizontal stylesheet for XML reports did not show step results beneath a sequence call with a terminated status. |
| 4C1ASN77 | Fixed an issue where TestStand disabled the buttons on the Additional Columns tab of the Import/Export Properties dialog box when you clicked the first element in the Values list. |
| 4AIFO1G0 | Fixed an issue where Property Loader steps returned an error when trying to import property values from database fields that contained NULL values. TestStand 4.0.1 ignores property values from database fields that contain NULL values. |
| 4CJERAYL | Fixed an issue where the text was missing on the Reset All Data Sources to Default button on the Data Source tab of the Edit Multiple Numeric Limit Test dialog box for a LabWindows/CVI user interface. |
| 47CAD977 | LabWindows/CVI 8.1.1 fixed an issue where a DLL built with LabWindows/CVI 8.1 or earlier using the ActiveX Automation Library leaked a handle when TestStand unloaded the DLL. For example, the leak occurred each time you selected Tools»Sequence File Documentation, which runs a sequence that called into a LabWindows/CVI DLL. You must recompile the DLL to prevent the DLL from leaking the handle. |
| 4DBF9LZL | Fixed an issue where instance properties of step types and data types became shared properties and you could no longer edit the values of the properties. This issue occurred when the type property for the instance enabled the PropFlags_Shared instance default flag. |
| 4DBFPVZG | Fixed an issue where TestStand returned an error for expressions that specified a variable or property that ended in ".Value". |
| 48H8L7MF | Fixed an issue where the edit panes for the Numeric Limit Test and the Multiple Numeric Limit Test steps did not update the numeric format of the measurement properties in the result. This issue prevented reports from displaying measurement data using the numeric format you specified. |
| 4CBA4BU | Fixed an issue where a TestStand application returned a generic Runtime Error dialog box when Windows XP users with limited privileges launched the application. |
| 4DCAP43S | Fixed an issue where the .NET Adapter incorrectly returned zero for numeric array elements when you specified an expression or an individual array element. |
| 4BUHT00 | Fixed an issue where two nested types were not merged properly when a type conflict occurred. |
| 4D4A09B8 | Fixed an issue where the AutoSchedule step type example did not fit in 1024 x 768 resolution. |
| 4DG7SUUZ | Fixed an issue where installers the Deployment Utility created did not include all the dependencies for the Database and Property Loader step types. |
| 4DJBD0RA | Fixed an issue where a Call Executable step that ran on a remote server no longer worked when you saved the file as a TestStand 3.5 file and the step did not specify a password. |
| 4DJA7DYL | Fixed an issue where TestStand returned an error when you created code using the default template for the C/C++ DLL Adapter. |
| 4DNF6TB8 | Fixed an issue where TestStand incorrectly marked step types as modified when you saved sequence files as TestStand 3.5 or earlier files. |
| 4DPC9B77 | Fixed an issue where TestStand would hang when a step in an execution called the GetSequenceFileEx method to load a sequence file and TestStand launched the Type Conflict In File dialog box. |
| Bug ID | Fixed Issue |
| Sequence Editor |
| 3PKEGNRA | Fixed an issue where the Filter tab of the Find in Files dialog box incorrectly excluded adapters that you configured as hidden. |
| 3709SIG0 | Fixed an issue where sending a UIMsg_OpenWindows message for an unsaved file to the sequence editor failed to open a window for the file and the sequence editor generated an error indicating that the directory could not be found. |
3KEET8MT
3LGDNHMF | Fixed an issue where the sequence editor did not update the execution entry points in the Execute menu when you changed the default process model in the Station Options dialog box or when the model file was loaded when previously not found. |
| 3Q9F1FJ6 | Fixed an issue where the sequence editor would hang or crash when creating code for a LabVIEW step. |
| 3R0L6HG0 | Fixed an issue where the Watch View incorrectly removed carriage-return characters from a watch expression when selecting the expression. |
| 3QIEFC26 | Fixed an issue where the sequence editor crashed when you attempted to open a large number of files. |
| 3BK9B0B8 | Fixed an issue where the sequence editor did not refresh execution windows to reflect breakpoint changes when you loaded a different workspace. |
| 39693SB8 | Fixed an issue where attempting to edit extremely large string values in the sequence editor made the application hang. |
| 3U5F2PNX | Fixed an issue where TestStand prompted you to save a type palette file when closing the sequence editor, even after previously saving the file. |
| 3K3DSTGH | The LabWindows/CVI 8.0 and later Run-Time Engine fixed an issue where the sequence editor leaked memory every time it was deactivated and reactivated. |
| 3RE8S6FK | Fixed an issue where TestStand generated an error when you tried to save a sequence file after editing a custom data type. |
| 3KL7QKUZ | Fixed an issue where inserting code modules on a sequence file in a workspace incorrectly added temporary VIs to the workspace when steps in the sequence file called Express VIs. |
| 3A8CDMRA | Fixed an issue where the Watch View did not highlight a watch expression in red when the 'On True' watch breakpoint setting suspended the execution. |
| 3ALCSSRA | Fixed an issue where the Watch Expression Settings dialog box discarded changes when you enabled Exist Only in Specified Scope but you did not specify a sequence file. |
| 47F9LFG0 | Fixed an issue where the sequence editor and the Report View control leaked memory when displaying XML reports. |
| User Interfaces |
| 36PAB7G0 | Fixed an issue where an open VB.NET and C# TestStand operator interface cancelled a request to shut down Windows 2000. |
| 45FLMBG0 | Fixed an issue where TestStand did not prevent you from attempting to run a second TestStand UI application in the LabVIEW development environment while another TestStand UI application was already running. |
| UI Controls |
| — | TestStand 3.5 and later fixed an issue where the ApplicationMgr.OpenSequenceFile method threw an exception if a type conflict occurred. The method now returns NULL, and TestStand fails to load the file. |
| 3A8AQQLW | Fixed an issue where a call to the SequenceFileViewMgr.Refresh method removed highlighting for the currently selected steps. |
| 3ERB3NYL | Fixed an issue where TestStand did not trace execution of the LoginLogout callback when you enabled the Trace Into Separate Execution Callbacks station option. |
| 3M7F4U3 | Fixed an issue where TestStand failed to process the command-line arguments when the ApplicationMgr.LoginOnStart property was False. |
3O4E4UMT
3H6F9DMT | Fixed an issue where the TestStand UI Controls did not display tip strips when used in a LabVIEW operator interface. |
| 3O4D5BMT | Fixed an issue where the ReportView control did not display an empty report when you called Report.Reset(""). |
| 3W4BN7B8 | Fixed an issue where TestStand UI Controls on LabWindows/CVI child panels moved off screen when resizing the control using their borders. |
| 3OO153MF | Fixed an issue where the SequenceView UI control did not auto-size the Description column when double-clicking the column divider. |
| LabVIEW |
| 3QG9N300 | Fixed an issue where a small memory leak occurred when TestStand used the LabVIEW 8.0 Run-Time Engine to call a VI that displays and closes its front panel. Use LabVIEW 8.0.1 to prevent this memory leak. Alternatively, you can call the VI without displaying the front panel, or you can configure the LabVIEW Adapter to execute VIs using the LabVIEW 8.0 development system. |
| 3Q9CKF00 | Fixed an issue where TestStand could not use LabVIEW 7.1.1 or earlier to call a remote VI that has a TestData control wired to its connector pane. Use LabVIEW 8.x to resolve this issue. |
| 464C8S77 | The LabVIEW 8.0 Run-Time Engine and later fixed an issue where TestStand crashed when attempting to load a DLL created in LabVIEW 7.0, the LabVIEW 7.0 Run-Time Engine was not installed, and the DLL incorrectly used a different LabVIEW Run-Time Engine. This issue does not occur if you create the DLL using LabVIEW 8.0 or later. |
| 3M1B99RR | Fixed an issue where an error occurred and closed the LabVIEW Specify Module dialog box when adding elements to a 1D cluster array. |
| 3VQCBA5E | Fixed an issue where the LabVIEW Adapter could not call VIs that wire Generic IO references to the connector pane because the LabVIEW Adapter incorrectly interpreted the terminals as Number (U32). |
| 3IOEG84E | Fixed an issue where the LabVIEW Adapter incorrectly created a new data type for cluster parameters that contained an array of clusters. |
3BK9OBGH
3KRG3RGH | Fixed an issue where the LabVIEW Specify Module dialog box did not allow you to specify a value for a required parameter if the step was previously configured to pass a default value when the parameter was not required. |
| 3ZGG3300 | Fixed an issue where you could not edit array elements previously specified on the LabVIEW Specify Module dialog box after decreasing the default array size on the control in the VI and reloading the VI prototype. |
| 3A9AG8J6 | Fixed an issue where the LabVIEW Adapter parameter mapping feature no longer worked for a step when the step type used a default Express VI as its module and you deleted mapped values applied to the step the last time you configured the step. |
| 3BRCHDRA | Fixed an issue where TestStand would hang while executing a VI that called Exit and the LabVIEW Adapter was running VIs in the LabVIEW development environment. |
| 3B0L59UZ | Fixed an issue where the LabVIEW Adapter waited until shutdown to clean up temporary wrapper VIs that were created when configuring and running Express VIs. |
| 3BLANJB8 | Fixed an issue where the LabVIEW Adapter incorrectly removed the variable prefix from a property in a parameter expression when configuring an Express VI. |
| 3B791NB8 | TestStand 3.5 and later fixed an issue where the LabVIEW Specify Module dialog box silently discarded parameter values when reconfiguring an Express VI and the parameter names for the VI changed. |
| 3WD79II0 | Fixed an issue where the LabVIEW Specify Module dialog box incorrectly decremented the enumeration value of a parameter of a VI for digital display controls. |
| 3R2FCL4E | Fixed an issue where TestStand always generated a type conflict when opening a file that used a data type that contained a LabVIEWClusterArray property and the same data type was already loaded. |
| 3WIC6UQ2 | Fixed an issue where the LabVIEW Adapter could not pass an array of Data Log File references to a VI. |
3W64RRCM
3WA6QKPT | Fixed an issue where TestStand would hang or crash when calling a LabVIEW VI that included a control inside a tab and the control was wired to the connector pane. |
| 3ZIBR00 | Fixed an issue where the LabVIEW Adapter did not remap parameter values correctly after changing wired terminals for the VI and reloading the prototype. |
| 3X98OGW3 | Fixed an issue where calling a LabVIEW VI using a LabVIEW Run-Time Engine generated an error if the step passed a string value that started with "LVSTR:". |
| 3RFD033S | Fixed an issue where the LabVIEW Adapter returned an error when using the LabVIEW development system to call VIs that returned a Modular Instruments session. |
| 3V67T88P | Fixed an issue where TestStand would hang or crash when calling a VI in which the label for a wired control or indicator of the VI ended with a space character. |
| 3TUC02W3 | Fixed an issue where calling a LabVIEW VI using a LabVIEW 8.0 Run-Time Engine generated an error if the step returned a VISA session. |
| 3S1CPSBK | Fixed an issue where TestStand crashed if you terminated the LabVIEW 8.0 development system while executing a VI. |
| 3KS9OKGH | Fixed an issue where the LabVIEW Specify Module dialog box did not clear the description and context help link text when changing an Express VI call to a standard VI call. |
| 3ZHCQT00 | Fixed an issue where the LabVIEW Specify Module dialog box did not check the data type of parameters that TestStand passed to 2D array indicators. |
| 3JNAHRJ6 | Fixed an issue where TestStand crashed when you attempted to create code using the LabVIEW Adapter and the LabVIEW development system was not installed. |
| 3KRFO2GH | Fixed an issue where the LabVIEW Specify Module dialog box incorrectly reported an error when you did not specify an expression for the Element1 property of a DynamicData parameter. |
| 3ZBF9800 | Fixed an issue where the LabVIEW Specify Module dialog box cleared the expressions specified for real or imaginary elements of complex parameters when reloading the prototype for the VI. |
| 3ZCIH077 | Fixed an issue where the LabVIEW Adapter did not filter out HTML tags, such as bold, from error messages. |
| 3OUFPBG0 | Fixed an issue where the LabVIEW Specify Module dialog box incorrectly displayed "1D Array" for the real and imaginary elements of a 2D (or more) complex array parameter. |
| 3QBCKO77 | Fixed an issue where the LabVIEW Adapter did not release a reference to a remote VI after unloading all modules. |
| 3PLEDUM0 | Fixed an issue where calling the Read From Measurement File Express VI returned error code 100. |
| 3QHH3RGH | TestStand 3.5 and later fixed an issue where the LabVIEW Specify Module dialog box generated an error when adding elements to any array item within a 2D array of clusters. |
| 2YGG9200 | LabVIEW 8.2 and later fixed an issue where ActiveX controls, such as the TestStand UI Controls, did not respond to mnemonic keys. |
| 2ZM2FG0 | Fixed an issue where the LabVIEW Adapter leaked memory calling VIs with waveform parameters. |
| 46R964UZ | Fixed an issue where the LabVIEW Adapter reset the Propagate to Subsequence and Allow Propagation from Caller properties on local variables when assigned a waveform value returned from a VI. |
| 40TE6O3Q | Fixed an issue where the LabVIEW Specify Module dialog box cleared parameter expression values of cluster elements after configuring the Express VI. |
| 3BND14GH | Fixed an issue where a LabVIEW operator interface would hang if an execution preloaded a module for a remote VI call when starting the execution. |
| 3BE9KPB8 | LabVIEW 7.1.1 and later fixed an issue where LabVIEW lost focus when dismissing a property page for a TestStand UI control. |
| 41JGQ1BU | Fixed an issue where a LabVIEW operator interface executable would hang closing the application if you previously executed a remote VI call. |
| 3ZDCENI0 | Fixed an issue were the LabVIEW Adapter generated an error when calling a VI that contained a String control that you changed to a Path control. |
| 3ZIA9VOF | Fixed an issue where the LabVIEW Specify Module dialog box generated an error when attempting to create a TestStand data type for a parameter that contained an array of LabVIEW I/O controls. |
| 461A6654 | Fixed an issue where the LabVIEW Adapter generated an error when trying to call a VI on a LabVIEW 8.0 Real-Time Module system. |
| 43JJT1M7 | Fixed an issue where the LabVIEW Adapter incorrectly passed double-byte Japanese string data between TestStand and VIs when executing VIs using the LabVIEW Run-Time Engine. |
| 41J1LKL3 | LabVIEW 8.2.1 fixed an issue where TestStand UI Controls became hidden on LabVIEW front panels that you edit if TestStand previously executed a step that called a VI that used a TestStand UI control. |
| 3Q3DRE77 | LabVIEW 8.2.1 fixed an issue where TestStand would hang when executing the Undeploy operation of a Deploy Variables step in multiple threads. |
| LabWindows/CVI |
| 2XIC109Q | Fixed an issue where the LabWindows/CVI ADE required you to select Continue after you attempted to step into a DLL and LabWindows/CVI could not find the specified source file on disk. |
| 3QIC1VRA | Fixed an issue where the LabWindows/CVI Specify Module dialog box initiated editing in the Function Call control when you entered lowercase "step" or "locals" as an argument for a parameter. |
| 3BEB5HRA | Fixed an issue where expression combo boxes in LabWindows/CVI dialog boxes showed a display value in the control instead of the actual value when you used a mnemonic key to give it focus. |
| 3P0LAMGH | Fixed an issue where the LabWindows/CVI Specify Module dialog box read DLL export information and incorrectly interpreted CAObjHandle parameters as integer and incorrectly displayed type names for enum parameters. |
| C/C++ DLL Adapter |
| 3QIDDO6I | Fixed an issue where the C/C++ DLL Adapter did not update prototypes when you changed how a struct was passed, for example, pass by pointer and pass by value. |
| 3AD8KU6A | Fixed an issue where the C/C++ DLL Adapter could not edit code if the function definition in the source file used macros. |
| 3P8CRURA | Fixed an issue where the C/C++ DLL Adapter sometimes failed to properly insert code using Visual Studio when the function already existed as the last line and you inserted code below it. |
| 3BQ8TAYL | Fixed an issue where the C/C++ DLL Adapter generated an error when generating code with a _bstr_t parameter. |
| ActiveX/COM Adapter |
| 3T39G9BK | Fixed an issue where the ActiveX/COM Adapter incorrectly generated an error when the interface call returned False and no error object was returned. |
| .NET Adapter |
| 3QIGDN6I | Fixed an issue where the .NET Adapter incorrectly inserted an Imports statement before Option statements when generating code. |
| 39Q7ESYL | Fixed an issue where stepping into C# code while running multiple executions caused a system-level exception. |
| 3QIENBYL | Fixed an issue where Edit Code with the .NET Adapter did not work if the source code had duplicate TestStand API "using" statements. |
| 41BLCE00 | Fixed an issue where the .NET Specify Module dialog box did not allow you to specify default parameters for a constructor. |
| 45PBKPOF | Fixed an issue where the .NET Adapter leaked memory when calling .NET assemblies that returned arrays. |
| 40M9KPUZ | Fixed an issue where the .NET Specify Module dialog box displayed 1D arrays of classes, structs, or enums as 2D arrays. |
| 40LF7LUZ | Fixed an issue where the .NET Adapter generated a system-level exception when calling a module where you specified to use the default value for an in/out parameter. |
| 4709M2YL | Fixed an issue where the .NET Specify Module dialog box displayed duplicate enum values using the name of the first value. |
| Deployment Utility |
| 2XMAA1G0 | Fixed an issue where the Deployment Utility taskbar item was not visible when you opened a modal dialog box. |
| 3RFBRPM0 | Fixed an issue where the Deployment Utility did not interpret paths properly for files located in the desktop, program menu, and startup directories on foreign operating systems. |
| 2XQEKRM0 | Fixed an issue where running the Deployment Utility crashed when running more than one instance of the application. |
| 3V0D5JI0 | Fixed an issue where the Deployment Utility could not deploy a VI Template when you configured the Deployment Utility to lock the block diagram of the VI. |
| 3SS8GQF5 | TestStand 3.5 and later fixed an issue where the Deployment Utility logged an error when building a deployment if you used Insert Code Modules on the sequence files in the workspace and the workspace included a sequence file that called an Express VI and another sequence file that called the first file. |
| 3BBGP2MF | Fixed an issue where the Deployment Utility did not prompt to save a modified .tsd file when loading another .tsd file using the MRU list of the Load button. |
| 3QDGFQGH | Fixed an issue where the TestStand Deployment Utility did not properly update the paths to the source files when you copied or moved a .tsd file to a new location and you opened and resaved the .tsd file without performing an analysis of the source files. |
| 3P5FG56I | Fixed an issue where the Deployment Utility did not reload updated TestStand search paths from disk before performing an analysis operation. |
| 3Q2HHRRA | Fixed an issue where the Deployment Utility erroneously logged a warning indicating that an LLB file could not be found when the path in the workspace for the file was an absolute path. |
| 3LC85AIA | Fixed an issue where entering a network path in the Installer Directory control generated an error while typing. |
| 3N5DKQM0 | Fixed an issue where the Deployment Utility did not list the National Instruments directory as a target for deploying files. |
| 3OSGP7G2 | Fixed an issue where the Deployment Utility did not allow you to create non-English based installers. |
| 3BBERU6A | TestStand 3.5 and later fixed an issue where the Hide License option in the Deployment Utility did not appear enabled when loading a .tsd file. |
| 40KMM4M7 | Fixed an issue where the Deployment Utility failed to warn you when you attempted to include files with dual-byte character names in an English installer. |
| 3RDE1RM0 | Fixed an issue where the Deployment Utility did not properly update VI module paths in steps when the called VI contained dual-byte characters. |
| Miscellaneous |
| 42BCLS00 | Fixed an issue where loading protected files generated unexpected type conflicts or unknown type name errors. |
| 47EGAK3S | Fixed an issue where an execution appeared to leak memory if a Sequence Call step executed a sequence in another file and the step was set to unload the module after the step executed. TestStand did not free the file globals for the sequence file that the step called. |
| 373B4HG0 | Fixed an issue where TestStand listed the "Containing project directory" as an option in the Edit Search Directories dialog box. The workspace uses the relative path from a file to the project file if valid. |
| 3KEBH1B8 | Fixed an issue where the Expression Browser dialog box did not allow you to insert subproperties into a container property. |
| 3DRA52MT | Fixed an issue where the Preconditions dialog box deleted an "AllOf" function if you entered a C++ style comment in an expression element of the precondition. |
| 3O4ESKMT | Fixed an issue where an Expression control incorrectly highlighted the FindFile function as an error when you passed a property that evaluated to an empty string at edit time. |
| 3EAAP8W3 | Fixed an issue where the Sequence Properties dialog box incorrectly attempted to validate expressions that apply only when the file type is a model. |
| 3SE2O1LL | Fixed an issue where the Preconditions dialog box prevented you from selecting a step that had a large number of characters in its name. |
| 3F5HE48A | Fixed an issue where TestStand incorrectly displayed the Advanced button when calling DisplayPropertiesDialog on a User object and you passed PropDlgOption_DisableAdvancedButton to the options parameter. |
| 3YFED9AF | Fixed an issue where selecting Loop on Selected Steps executed the steps inside a For Loop only once if the last selected step was the End step. |
| 3CUCA96I | Fixed an issue where TestStand did not update all expressions in a sequence that referenced a step when you changed the name of the step. |
| 39HFRT00 | Fixed an issue where TestStand did not allow you to replace an existing file when you attempted to save the file for an earlier version of TestStand. |
| 3BLFB8B8 | Fixed an issue where the Workspace Browser dialog box did not open non-sequence files in an external program when you double-clicked the file. |
| 3D6E7RZ8 | Fixed an issue where the For Each step did not assign a value to the current element value if the property was an instance of a custom data type. |
| 3UQ1CD8P | Fixed an issue where TestStand suppressed run-time error handling in 'Not Viewable' protected files by not calling PostStepRuntimeError callbacks until the run-time error propagated to a non-protected file. |
| 3YLABION | Fixed an issue where the privileges of a user became enabled when a user who did not have administrator privileges updated their password. |
| 3VU43BQW | Fixed an issue where the expression values on the Text and Buttons Tab of the Message Popup dialog box mirrored value changes you made to the Response String Length control on the Options Tab. |
| 3TFAHFI0 | Fixed an issue where the data for the graph control in TestStand XML reports did not appear because the Y axis range was incorrect. |
| 3YKAULUU | Fixed an issue where looping on a Sequence Call step and disabling Record Result of Each Iteration on the step caused the expand.xsl style sheet to incorrectly indent step results in the report. |
| 3VRGAGT3 | Fixed an issue where on-the-fly XML reporting failed to update the interim report unless the call stack depth was less than 3. |
| 3R0A3CG0 | Fixed an issue where the AddRootTagsToXMLReport function in ModelSupport.dll incorrectly changed CRLF to CRCRLF, which resulted in odd formatting when viewing the XML file. |
| 3U8DHRB8 | Fixed an issue where TestStand crashed when you changed the ExecutionViewMgr.StepGroupMode property while running. |
| 3QDBPHB8 | Fixed an issue where executing an AutoSchedule step a second time while running a sequence would hang if while running the first time you exited the block without completing the block normally. |
| 3QBE2DRA | Fixed an issue where clicking on some of the secondary dialog boxes that the Database Options dialog box displayed closed the dialog boxes without committing the changes. |
| 3T8D6AB8 | Fixed an issue where TestStand crashed when calling Engine.GetInternalOption(InternalOption_ApplicationManager). |
| 3P79DDB8 | Fixed an issue where TestStand crashed when you compared two context property values in an expression. |
| 3K7DD4MF | Fixed an issue where the CommentOf expression function returned an empty string when called on SequenceFile objects. |
| 3QIDL2RA | Fixed an issue where the Database Options dialog box discarded edits to a schema comment if you tabbed off the control. |
| 4661QKIZ | Fixed an issue where a Property Loader step failed when importing from a file that contained import data for a large array or container property. |
| 421D7CYL | Fixed an issue where TestStand reported property object leaks after a Sequence Call to a remote computer failed to access the system. |
| 425APA00 | Fixed an issue where Message Popup steps returned an error when executed on a remote computer that you call using a Sequence Call step. |
| 467AHKYL | Fixed an issue where the array data was incorrectly interpreted when displayed in the graph of an XML report on a system configured to use commas as decimal points. |
| 43JFG3B8 | Fixed an issue where a Do While step incorrectly evaluated its condition for its first loop if you previously executed the loop and you branched out of the loop to restart the loop again. |
| 44IDMK7K | Fixed an issue where the TestStand Database Viewer generated an empty error message when attempting to open an invalid data link. |
| 46PF9MUU | Fixed an issue where XML reports that used the horizontal stylesheet did not display if a Multiple Numeric Limit Test step returned an empty array with no measurements. |
| 41E86U77 | Fixed an issue where the Property Loader incorrectly created database columns using the varchar data type instead of a numeric data type. |
| 41HCK7G0 | Fixed an issue where the Application Manager generated an error when returning from an ApplicationMgr.UIMessageEvent event for a custom UIMessage. |
| 447GTM7 | Fixed an issue where an error occurred in process models when attempting to generate a report if the sequence file pathname contained specific Japanese characters and TestStand was generating the report in the same directory as the sequence file. |
| 35BG11B8 | Fixed an issue where TestStand supported only 256 colors for icons. TestStand now supports 16-, 24-, and 32-bit icons. |
| 3Z6AH8CN | Fixed an issue where the IVI-C Switch step used a semicolon instead of a comma as a delimiter for Init options when trying to simulate the instrument, which resulted in the step using the real instrument when present. |
| 3V9G93IF | The LabVIEW 8.0 Run-Time Engine fixed an issue where Visual Studio displayed the following prompt: "Managed Debugging Assistant 'LoaderLock' detected a problem in SeqEdit.vshost.exe" when the sequence editor loaded the LabVIEW 7.1 Run-Time Engine while debugging TestStand with Visual Studio and you enabled Managed Debugging Assistant on the Exception dialog box in Visual Studio. |
| 47L5HNM | Fixed the documentation for the Replace expression function, which incorrectly stated that the function returned the modified string. |
| — | TestStand 3.1 and later fixed an issue from TestStand 2.0.x where the DLL Flexible Prototype Adapter incorrectly handled calls to AddRef() and Release() on references in structure parameters or arrays of structure parameters when the value of a reference that was passed to the code module was different than the value the code module returned. If you attempt to run the TestStand 2.0.x example located in \Examples\StructPassing\C or any code module based on this example in TestStand 3.1 and later without properly handling references, TestStand might crash. The TestStand 2.0.x version of this example failed to properly call AddRef() and Release() on references in structure parameters that the code module used. The C/C++ DLL Adapter in TestStand 3.1 and later resolves this issue, and the TestStand 3.1 and later examples properly demonstrate how to use references within structure parameters. |
| — | TestStand 3.0 and later fixed an issue where the order of execution for the Pre and Post Interactive callbacks was incorrect for steps that run in a root interactive execution. In TestStand 2.0, the order of execution was Setup Step Group, Pre Interactive Callbacks, Selected Steps, Post Interactive Callbacks, and Cleanup Step Group. In TestStand 3.0 and later, the order of execution is Pre Interactive Callbacks, Setup Step Group, Selected Steps, Cleanup Step Group, and Post Interactive Callbacks. |
| — | TestStand 3.5 and later fixed an issue where the Edit String Value Test dialog box persisted as "\r\n" in the Expected String Value control. TestStand now persists "\n" instead. |
| — | TestStand 3.1 and later fixed an issue where the Microsoft Internet Explorer ActiveX control TestStand used to display HTML and XML reports in the sequence editor report tab and the Custom UI Report did not always release its internally allocated memory each time the Internet Explorer control updated the report. If you update the control continuously over an extended period of time, the TestStand process memory use increases. TestStand 3.0 used the control in such a way that the failure to release memory occurred more often. TestStand 3.1 and later contain workarounds that limit the amount of memory the control fails to release. When you use on-the-fly reports, TestStand uses the Internet Explorer control only when the control is visible. |
| 320FDRMT | TestStand 3.1 and later fixed an issue introduced in TestStand 3.0 where if you opened a TestStand 2.x sequence file that contained a custom step type in TestStand 3.0, TestStand 3.0 incorrectly turned off the Instance Default Flag, PropFlags_SharedAtRunTime, for the Step.TS property. A side effect of this change is that in TestStand 3.0, instances of this type ignore run time changes to built-in step properties and code module settings. For example, if a step altered the precondition of another step at run time, the precondition change was ignored.
TestStand 3.1 and later fix this issue by reverting the flag back to its proper state when loading a TestStand 3.0 file. TestStand does not mark the step type as modified.
To prevent the fixed version of a step type in TestStand from being used in or accidentally propagating back to earlier TestStand sequence files, enable the Set Earliest TestStand Version that can Use this Type setting on the Version tab of the Step Type Properties dialog box and set the earliest version to the current version of TestStand. |
| — | NI-VISA 3.1 or later and NI-DAQmx 7.2 or later fixed an issue where the NI-PAL Service Manager (nipalsm.exe) generated an error each time you restarted the system. |
发表于 2020-2-29 12:50:55
