NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Modal Popup Issues

Why don't you post your VI. When I mentioned local variables, I don't mean TestStand locals. I was referring to LabVIEW locals.
0 Kudos
Message 11 of 21
(1,882 Views)
Sorry for the slow reply... this is something similar to the VI I am using. I can't post the original one because of NDA
0 Kudos
Message 12 of 21
(1,875 Views)
Same with this other dialog... so it looks like when I have dialogs in the process model callbacks something weird happens and I can't get the VI to be modal...
0 Kudos
Message 13 of 21
(1,870 Views)
I'm not sure why you have the Start/End Modal functions inside case statements and why you are reading the Fp.IsFrontmost property. That's not necessary, imho. Try it without the case statements and without the property node.
0 Kudos
Message 14 of 21
(1,853 Views)
I'm wondering if I'm using the Start/end modal routines properly.  I run this code (called from TestStand) and it still shows up behind my TestStand OI.  Fortunately, it's larger than the OI, so I realize it has popped up, and I don't sit there wondering what's going on.
0 Kudos
Message 15 of 21
(1,850 Views)
Change the window appearance to be modal in the VI Properties.
0 Kudos
Message 16 of 21
(1,847 Views)
I have the Start/End Modal functions inside case statements and the Fp.IsFrontmost property because I am detecting if the VI is already modal first, if it is not then I make it modal to TestStand. When I do not do this and leave the Start/End Modal functions by default my VI FP flashes when is shown and this confuses the operators.
0 Kudos
Message 17 of 21
(1,841 Views)
That doesn't explain much to me. How can the VI be frontmost first? Are you calling this VI in multiple threads so that it might not be closed when you call it again? Are there other VIs that could be open when this is called? If so, and those are set to be modal (LabVIEW modal), then that will be a problem.
0 Kudos
Message 18 of 21
(1,832 Views)

That's exactly what I do not understand, the VI is set to be modal and has the Start/Stop Modal subVIs inside without any case condition so it appears modal for a fraction of second then disappears and it appears again, I guess, after running the StartModal subVI. What I do not know is why it disappears...

Now, when I run it without the Start/Stop Modal subVIs it appears modal most of the times but still sometimes, specially after running several sequences continously, it appears behind the LV Application Window and I can not continue testing. I have to quit LV and this causes the C++ error I shown in one of the previous posts. What is strange is that this did not happen with the previous versions of LV and TS I was using before (LV7.0 TS3.0)

Ideas?

0 Kudos
Message 19 of 21
(1,822 Views)
The latest version I can test with is TestStand 3.1 and LabVIEW 7.1 and it all seems to work just fine there. Maybe someone with a later version can figure out what is happening.
0 Kudos
Message 20 of 21
(1,816 Views)