LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Display Message To User subVI

Hello, 

Has there ever been a fix for this? I am on LabVIEW 2019 and I am having issues with the Display message to user subvi disappearing from my vi's. There doesn't seem to be any reproducibility for this other than executing the .seq file and seeing if the display message to user boxes are missing. 

I've got a sequence that uses a large amount of display message to user boxes, however only the latter half of the test has this issue. Not one to revive a nearly decade old issue, but apart from replacing all of these subvis with the one dialog function I would expect it to be working as intended. 

Any advice would be greatly appreciated,

Many thanks,
njo

0 Kudos
Message 1 of 3
(192 Views)

@HatnanJo wrote:

Hello, 

Has there ever been a fix for this? I am on LabVIEW 2019 and I am having issues with the Display message to user subvi disappearing from my vi's. There doesn't seem to be any reproducibility for this other than executing the .seq file and seeing if the display message to user boxes are missing. 

I've got a sequence that uses a large amount of display message to user boxes, however only the latter half of the test has this issue. Not one to revive a nearly decade old issue, but apart from replacing all of these subvis with the one dialog function I would expect it to be working as intended. 

Any advice would be greatly appreciated,

Many thanks,
njo


I split this off to a new thread.  I think you have a slightly different problem here.  You see, I have a magic 8-Ball that started spinning when you mentioned ".seq file."

 

That makes me suspect that you are using the TestStand Display Message to User.vi.

 

If so, that vi is stored inside one of those TestStand support folder.  The darned vi is supposed to be saved with the VI Property FP.Behavior = modal.  Sometimes that property gets overwritten by mistake; Usually when some developer hangs LabVIEW by having a non-running Modal FP open.  

 

I even authored a Champion Tip  for a previous contract that explains in detail how this commonly happens, why the "Revolke All Modal.vi" is dangerous, how the existing shipping Dialogs and Prompts are obsolete and how to write your own replacements that don't crash.


"Should be" isn't "Is" -Jay
0 Kudos
Message 2 of 3
(149 Views)

There's TS support functions with Make Modal or something that's quite helpful, but it still happens that they land behind TestStand, but mostly when i have LV with windows open to debug.

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 3 of 3
(98 Views)