Eagerly awaiting Teststand 2024

[ShockHouse]

"C:\ProgramData\National Instruments\TestStand 2024 (64-bit)\Cfg\UISettings.json"

Looks like all the colors are here in Decimal form (RGB). Although if I try to change this, it just gets reverted back when TestStand loads. So maybe some setting will allow us to actually change all the colors.

[bienieck]

This file is there for years already. I doubt you can change UI colors. Only step list is configurable (and always was).

[HarshaBhushan]

Modern operator interface is under work. It will be available in 2025.

[HarshaBhushan]

You can refer to the release announcement here.

[MichaelS78]

I hope 'Modern User Interface' does not refer to the 'Modern' controls in LabVIEW 😂

At least I can see toolbar buttons again but it's going to take some getting used to the adapter icons.

[HarshaBhushan]

As part of Modern user interface, we are coming up with web based controls (as an alternate to the current ActiveX controls). We are targeting enabling creation of interfaces using these controls & using web frameworks (like Blazor) to begin with. These would be made available in LabVIEW too in time.

Thanks for your feedback on the UI. We do plan to address them incrementally over the releases. 

[bienieck]

Am I guessing correctly that there will be a TS server and a Blazor-based web UI for communicating with this server? In that case, will I be able to have my TS UI in e.g. Electron? Or maybe it's too early to ask such questions?

[ee-jallen]

Can you clarify what this means?

Reusing sequence files across TestStand versions

Starting this release, sequence files can be used across versions of TestStand without re-saving. This would be supported across versions where there aren’t breaking changes, this is indicated by change in the engine version number (which can be found in Help >> About TestStand) 

Does this mean that a future TS2025 version sequence file would work with TS2024 without using Save As 2024?

[HarshaBhushan]

>>Can you clarify what this means?

>>Reusing sequence files across TestStand versions

You can find more details here.

Essentially, we won't be updating TestStand engine version every release. We will do it only if absolutely necessary (eg: we introduce new step types). So this just means you will end up needing 'Save' or 'Save As' less often.

A sequence file created in a later version would work with an older version of TestStand provided the engine versions are the same (i.e there were no compatibility breaking changes between those TestStand versions).