Hi,
After having some trouble and performances issues with my custom LabVIEW User Interface for one of my TestStand project, I discovered that Top level VI (Main and Launcher) are configured to run in User Interface Thread in LabVIEW.
My OI are based on the Full Featured LabVIEW UI Example and I just check, with TestStand 2014 and 2016, both have the LabVIEW VI configured in this way ?
Is there any reason do to that ?
As LabVIEW Developper, for me this is a big mistake. This can be a real mistake when we read this KB .
if the VI calling TS API are configured to run in "Same as caller" Thread, they are running in the UI Thread by Default.
Is it a mistake of the developer of the User Interface Example or I missed something ?
Best regards.