Prompt user for input behaving as a vi

[jayelle]

I have a weird problem.

When I run a program that has two "prompt user for input" sub vi's in a row, the first one does exactly what it is supposed to.  The second opens like a Labview VI.  This means you cannot use it as intended and so the larger program that  it is a part of cannot run.  I think this problem started spontainiously as I did'nt change that part of the program at all.   I even tried deleting the old sub vi and replacing it with a new one and the problem persists. Any thoughts on this? Attached is the program and a picture of what the error looks like. Sorry the program is big but the problem occurs in the first few steps. 

Thanks,

Jo

[James.M]

I'm not seeing what you're seeing, so I think it's a problem with your install. Does the same thing happen when you change the order of the popups? Is there a way to make it appear like it should?

Here's what I see:

[Jordan_M · Accepted solution]

Hi Jayelle,

The problem probably isn't with your user input vi's, it is probably in the top loop of your program.  I think that your second input vi opens, then your top loop starts running before the user can enter anything, then there is an error in the top loop which stops LabVIEW and leaves your dialog box open.  You can watch this happen if you open the block diagram and turn on "Highlight Execution".

[jayelle]

Changing the order of the popups at least made it run but the sub VI is still opening like a program.  I think you are right and it is the install that is messed up.

[James.M · Accepted solution]

---

@Jordan_M wrote:

Hi Jayelle,

The problem probably isn't with your user input vi's, it is probably in the top loop of your program.  I think that your second input vi opens, then your top loop starts running before the user can enter anything, then there is an error in the top loop which stops LabVIEW and leaves your dialog box open.  You can watch this happen if you open the block diagram and turn on "Highlight Execution".

---

Jayelle, is your program still running when the dialog looks like this? Jordan may be right that the code has stopped operating while the dialog is open. I had assumed that when you said it looked different, you knew that the code was still running. You can fix this if this is the case, buy just wiring your error clusters so that the loops don't start until after the dialogs.

Edit: Yeah, dude, looking at your screenshot: your code stopped running while the dialog was still open. The reason this wasn't a straightforward obvious thing is because code normally doesn't stop like this, but you put a STOP node in there. Don't do this. Like I said in one of your other posts, there are better ways.

The reason it worked when you switched the order of the popups is because that second from last popup's data must be collected before the loop that errors out can begin.