LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Prevent Block Diagram from hiding things when scrolling

Solved!
Go to solution

Hello, I would like to know where can I modify the Block Diagram to ensure it prevents this from happening? 

 

Is there a way? 

 

 

Blancoys_0-1649671426203.png

 

Thank you for your time! 

 

 

 

0 Kudos
Message 1 of 7
(1,994 Views)
Solution
Accepted by topic author Blancoys

Right-click the structures and select "Auto-grow". This will prevent you from being able to make it smaller than its contents.

 

Also under Options, select on the category "Block Diagram" "Place structures with Auto Grow enabled" should be checked (set to true).

Message 2 of 7
(1,984 Views)

Thanks a lot! 

0 Kudos
Message 3 of 7
(1,953 Views)

Of course, this is just a Band-Aid for "don't make the block diagram so big".  (IMO you should never need a main loop so big.  Or any loop, really.)

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
Message 4 of 7
(1,945 Views)

Agreed, but in fairness, when stuff is hidden, you can't actually know how large the diagram is vs how large it looks.....

Message 5 of 7
(1,939 Views)

I would note that there is an alternate solution - VI analyzer.  It doesn't check it in real-time like auto-grow, but it checks for anything hidden outside structure borders (as well as dozens of other problems).

 

I personally loathe auto-grow being on when using structures and I run a script to turn it off on all of my code if I ever get code from someone else that uses it (modified Nattify code).  The problem is that auto-grow not only stretches the code for what it's in, but also anything "underneath" it in another frame of a case structure or event structure.  So when I'm working on a case structure with 20 frames for a state machine or whatever, and auto-grow stretches out a case structure in one of those frames and I don't notice, and I save the VI, I now have 19 frames with their wires all with extra bends in them.

Message 6 of 7
(1,911 Views)

@Kyle97330 wrote:

I would note that there is an alternate solution - VI analyzer.  It doesn't check it in real-time like auto-grow, but it checks for anything hidden outside structure borders (as well as dozens of other problems).

 

I personally loathe auto-grow being on when using structures and I run a script to turn it off on all of my code if I ever get code from someone else that uses it (modified Nattify code).  The problem is that auto-grow not only stretches the code for what it's in, but also anything "underneath" it in another frame of a case structure or event structure.  So when I'm working on a case structure with 20 frames for a state machine or whatever, and auto-grow stretches out a case structure in one of those frames and I don't notice, and I save the VI, I now have 19 frames with their wires all with extra bends in them.


I've gotten used to it.

I pre-emptively stretch my diagrams now.

Although I do wish there were two separate options, don't shrink to cover code and Auto-grow

Message 7 of 7
(1,900 Views)