LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Default to Block Diagram?

Is there a way to make my VI default to the Block Diagram whenever I open it?

Most of the Front Panels on my VIs are fairly simple. I know I can open the Block Diagram with CTRL+E, but it turns the simple act of opening my Block Diagram into a two step process - every time.

There is probably an option somewhere that I can use to specify how LV opens VIs, but I can't find it.

I would really like my VIs to open back up to the same state they were in when I closed them. That is, if the Front Panel and Block Diagram are both open when I close the VI, they both open the next time I open that VI.

On a related note: How can I specify the default size for a new VI? Currently, all new VIs are large, and nearly fill the screen on my 1920x1200 display. That is a little too big! I'd like to have a way to tell all new VIs to start out no larger than 640x480 or something like that. If I need it bigger, I'll make it bigger.

\
Angus Cattle from Pool Ranch and Steel Repairs via Joe's Welding.
Message 1 of 9
(4,598 Views)
In the option menu, goto "Environment" and allow drop through clicks.

Now you can hold "CTRL" and double click to directly open the block diagram.
Regards,
André (CLA, CLED)
Message 2 of 9
(4,594 Views)
I'm using version 8.5, and that doesn't seem to work on mine. Whenever I hold down CTRL and double-click, I get a new label on the Front Panel.

Further, the act of opening my VI and then holding down CTRL while double-clicking still constitutes a two step process - which I am trying to get away from.

I want my VIs to open straight to the Block Diagram whenever they are opened.

Can this be done?

\
Angus Cattle from Pool Ranch and Steel Repairs via Joe's Welding.
0 Kudos
Message 3 of 9
(4,587 Views)

jp2labview wrote:
I'm using version 8.5, and that doesn't seem to work on mine. Whenever I hold down CTRL and double-click, I get a new label on the Front Panel.
You misunderstood. "Ctrl+double-click" is for opening a subVI that is located on the diagram. Do it on an icon on the diagram and it will open the subVI with the diagram window in front. Try it!
 
Message 4 of 9
(4,578 Views)
The question is:

Whenever I open a VI from the "File | Open..." menu or from the recent files list, how do I get it to open in the Block Diagram?

\
Angus Cattle from Pool Ranch and Steel Repairs via Joe's Welding.
0 Kudos
Message 5 of 9
(4,569 Views)
"Whenever I open a VI from the "File | Open..." menu or from the recent files list, how do I get it to open in the Block Diagram?"
 
You can't!
 
That option simply does not exist in LabVIEW.
 
It would be possible to write some code that would track which VI's were open, keep a file updated, and then open all of the BD when you want...
 
BUT
 
without writting the code to do that, it can not be done.
 
Just trying to help,
 
Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 6 of 9
(4,562 Views)
Following up on Ben's response, you could do something like the attached (LabVIEW 8.2). Just have it running while you work. Note that I just whipped this up quickly so there's bound to be possible side-effects in its operation. Modify as you need if you wish to use it.

Side-note: I tried to use the "Application: OS Open Document" event to do this example, but I that event never seemed to fire, which is why I resorted to the "VI Activation" event. I would have thought, based on its name, that it would fire when you opened a VI, but I couldn't get it to fire regardless of how I opened the VI. Anybody know about this event?


Message Edited by smercurio_fc on 12-04-2007 01:24 PM
Message 7 of 9
(4,540 Views)

Mercurio,

There is someone on the LAVA forum who's signature reads something to the effect "Listen to the experts when they tell you what is impossible. Then go do it.".

I'll try to remember to get back to this when I am on a machine with 8.2.

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 8 of 9
(4,528 Views)
Actually, it does exactly what you said:
"without writting the code to do that, it can not be done."
I should have also mentioned in my post that it uses a private property, so the property is not documented, nor guaranteed to still work in future LabVIEW versions.
0 Kudos
Message 9 of 9
(4,524 Views)