can't open subVI by double clicking

[oyester]

This is just irritating the heck out of me. I have a subVI that doesn't seem to be working as I think it should. I'm not sure if it is my problem or the subVI's.  But that's not what's bothering me.

If I double-click on the subVI icon (on the back panel of the parent subVI) nothing happens. The subVI does not open. If I right click on the icon and select Open, then the subVI will open. I can open all of the other subVIs on the back panel by double clicking on their icons.What parallel universe have I accidentally entered and how do I get back. I have two hungry daschunds waiting for me.

[altenbach]

Interesting.

Does the problem persist if you move it to a new diagram? If so, would you mind attaching it here?

What is your LabVIEW version?

[smercurio_fc · Accepted solution]

Here's one possible cause: Your VI's icon is not "closed". Check your icon to make sure there's a closed boundary on it. If you have an opening on the boundary then the white space will be "unclickable" (especially if you have the automatic tool selection on).

Message Edited by smercurio_fc on 11-05-2008 09:27 AM

[smercurio_fc]

For example, for this icon:

 

You cannot double-click in the white area, but you can double-click on the small graphic of a scope that's inside. Be sure to check each icon variant: "B & W", "16 colors" and "256 colors".

Message Edited by smercurio_fc on 11-05-2008 09:31 AM

[oyester]

It seems that things are MUCH worse than I thought. I was trying to strip down my main VI so that I could send it to this forum. I deleted a superfluous control, and got a broken arrow, as expected. I clicked on the broken arrow and the error list came up as expected. What I didn't expect to see was the "LabVIEW 8.6 Development System" window informing me that they had "encountered a problem"....

So basically I have a main VI that has confused the g-compiler (?) so badly that it can't tell me whats wrong. This VI is revision 4278 of a program that was started over ten years ago. It's more than 1.3 million bytes big. How do you fix a program that dies every time you ask it what's wrong with it?

[oyester]

By the way. How you you add images to a message?

[smercurio_fc]

You have to add the images as attachments so they're uploaded to the NI servers. You cannot have them point to your local machine.

In terms of your problem: I thought you said the problem was with a subVI, and not your main VI. In that case I'm not sure why you're messing with the main VI. Also, the size of your main VI tells me you have a monolithic structure. You should probably be using more subVIs rather than putting all of the code at one level. 

[oyester]

I said I couldn't open the subVI. I didn't know if the subVI or its parent was the problem. I'm embarrassed to admit it, but it turns out mercurio had the winning solution.

Also, LabVIEW knows about the error-list-causing-crashes problem and has a (mickey mouse but it works) fix for it that involves putting a big cluster on my front panel.

I inherited this program. Most of the time I am busy trying to figure out if the user has found a bug or a really creative way of screwing things up, adding new features to the code, and getting out the latest executable along with the latest and greatest user manual. This is a small company. The previous programmer, who is now my supervisor, is a very talented electrical engineer whos code works fine but looks like a circuit board. There are several huge, complicated subVIs that I would love to refactor. According to the VI analyzer, this program has 600+ local variables and 300+ global variables. I would love to clean all of that crud up, but I don't get paid to fix things that already work. I am not allowed to use object oriented concepts or any kind of semaphores because they confuse my supervisor. I am working on getting them to let me use some kind of source control program. This program has close to 500 subVIs in it and keeping track of changes is becoming too time consuming.

[smercurio_fc]

---

oyester wrote:

According to the VI analyzer, this program has 600+ local variables and 300+ global variables

---

Don't let Ray (aka JoeLabVIEW) hear about this.