From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
04-03-2013 12:07 PM
Hello,
Can somebody explain to me what are those two error code mean from the attach code? Untitled 2 is the main code and untitled 1 is the sub vi.
thanks
04-03-2013 12:29 PM
Your Boolean control ("Boolean") is False, so your code tries to close the front panel using a reference to a VI from a Local variable that doesn't contain a valid VI reference. It won't contain a valid VI reference until you change "Boolean" to True.
You can wrap the FP.Close code in a Case structure and use Not A Number/Path/Refnum? to decide whether to execute it or not.
04-03-2013 12:53 PM
I wraped a case structure on the close statement, I still get an error code 1198 and 1149.
04-03-2013 12:54 PM
Why is it in a loop running as fast as possible?
Why is it trying to open and run the same VI over and over if the button is True?
Are you trying to test out some concepts with this main VI? If so, the loop architecture is causing you more problems with your test than the things you are trying to learn by running the test.
04-03-2013 01:13 PM
I am trying to create a pop up window when a button is pressed. The pop up window is an another VI.
Thanks
04-03-2013 02:32 PM - edited 04-03-2013 02:33 PM
I usually make my dialog vis responsible for their own FP State to avoid non-running non closeable modal vis from blocking the app instance. I even have a tmplate for them since the express vis all use polling.
12-23-2020 03:45 PM
Thanks Brian! I was searching for that post. Now I have a tag!