LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
JackDunaway

Allow ONLY the Block Diagram to be opened Without Front Panel

Status: New

Allow us to open only the BD by CTRL+Double Clicking on the VI in the project. Sometimes, it's not necessary to see the FP!

20 Comments
Alexander_Sobolev
Active Participant

Meanwhile (for the next 2 years) enjoy Ctrl-Key shortcut, (for those, who has not written it yet)

 

in thread

http://forums.ni.com/t5/LabVIEW/HIde-Front-panel-enjoy-Ctrl-Key-shortcut/td-p/1898303

SteenSchmidt
Trusted Enthusiast

@AQ: Just wanted to note that on Real-Time it's very common to not have the front panel of a VI available, so assuming the FP being always available is dangerous. But this idea of Jack's here is about being able to have the BD open only, and leave the FP closed. Not about having VIs without FP at all (that discussion is a totally separate one, which we will have hammered out in due time :-).

 

Cheers,

Steen

CLA, CTA, CLED & LabVIEW Champion
AristosQueue (NI)
NI Employee (retired)

Steen: Ah, but in real time there's no block diagram either. The diagram assumes the panel, but the run time does not assume either.

 

There is work being done to decouple diagram from panel in the editor, but it is slow going.

jqu
Member
Member

I find it a useful "workaround" to use the method FP.Open with state "Hidden" instead of FP.Close. This way the FP is gone, but the BD stays open.

jqu
Member
Member

BTW, this miserable piece of code has the often desired effect:

 

Open_BD.PNG

 

What is so difficult about it?

wiebe@CARYA
Knight of NI

>What is so difficult about it?

 

Closing the diagram leaves the front panel hidden, and as a consequence, in memory.

 

That could have serious consequences! If the VI is a clone (even if it's not), and the parent leaves memory, the VI will stay in memory because the front panel is not closed (but hidden). A normal VI can still be removed from memory by re-opening the front panel and closing it (still a hassle), but a clone is hard to close once the FP is hidden.

jqu
Member
Member

Right. Thanks for the comment!

 

But we're talking about dev-time, not run-time. So in this situation I honestly wouldn't care too much about unreachable VIs hanging around in memory. But more importantly, I think the code I've shown above does never open any clone, but always the original, doesn't it?

 

However, I also see some implications having a VI in memory that is not visible any more...

 

But it's a handy hack anyways 😉

wiebe@CARYA
Knight of NI

Dev time doesn't mean VIs aren't running. I open sub VIs from running VIs all the time.

 

CTRL+dbl click implemented as it is now does open a clone if the sub VI is reentrant.

 

For me it would be more convenient to CTRL+Click to open the FP and BD and then close the FP than to use a Sub VI and browse to open just the diagram? I was assuming the code you've posted was to be used in a right-click menu or something.

jqu
Member
Member

Yes, I agree, that would be more convenient.

 

I used the above code to create a kind of "drop down bar" on the lower edge of my screen, where I can drag&drop VIs (from anywhere, project explorer, windows explorer, another VI...) in order to open only the BD. Cannot attach the VI here unfortunately, but I made it floating etc. so it stays conveniently on top. Not sure I will continue using it anyways 😉

 

 

Petru_Tarabuta
Member

+1. I have just posted a related idea: Block-Diagram-Only VIs (VIs without a Front Panel)