LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

What causes block diagram to expand?

Solved!
Go to solution

Hello

 

I have this VI (attached). I've worked on it for several days with no problems, but today it suddenly began to act weird.

Whenever i move an element, add it or remove, drag new wires or anything at all anywhere on the block diagram, the timed loop and other structures within it expand a few pixels down and to the right. Didn't notice this happening in the event loop nor the first for loop, only the timed loop.

 

Since this started happening i also noticed that moving elements around the block diagram is laggy and not smooth at all.

 

Tried restarting LabVIEW, but it didn't help. No other VIs show this bug.

 

EDIT:

AeroSoul_0-1648038126663.png

AeroSoul_1-1648038172289.png

 

This is how much the structures moved in the time since bug started.

 

0 Kudos
Message 1 of 18
(2,620 Views)

Too much junk in one block diagram is what does it.  Not joking.  Literally, if you have too much stuff sprawled over too much real estate, you're going to run into some weird stuff as you start to exceed the maximum boundaries of a block diagram.

 

But this is not the case here.  The VI is well-organized.  Pre LV 2021 SP1 automatic wiring can go haywire in lots of different ways (sometimes even after turning it off!), and I think this is one of those cases.

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.
0 Kudos
Message 2 of 18
(2,602 Views)

There's a lot of useless stuff currently on the diagram, but it's far from large i think.

 

I use LV 2019 f2 32 bit version. 

If it is wiring going haywire, how would i fix this? And why does it only happen within timed loop, but not over whole diagram?

0 Kudos
Message 3 of 18
(2,592 Views)

Tried making a snippet and creating a new VI, but the snippet actually brought the bug over, so new VI had it too.

 

Is there anything i can do apart from recreating VI from scratch?

0 Kudos
Message 4 of 18
(2,578 Views)

@AeroSoul wrote:

Tried making a snippet and creating a new VI, but the snippet actually brought the bug over, so new VI had it too.

 


I have experienced the same thing a few times over the years and more than one LabVIEW version. Even on relatively small block diagrams and I never found the actual cause...

 


@AeroSoul wrote:

Is there anything i can do apart from recreating VI from scratch?


In my experience no.

 

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 5 of 18
(2,572 Views)

@RTSLVU wrote:



@AeroSoul wrote:

Is there anything i can do apart from recreating VI from scratch?


In my experience no.

 


Simple copy-n-paste works *sometimes*.

---------------------------------------------
Certified LabVIEW Developer (CLD)
0 Kudos
Message 6 of 18
(2,568 Views)

Sometimes mass compile fixes things.

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 7 of 18
(2,552 Views)
Solution
Accepted by topic author AeroSoul

This fixes it.

"If you weren't supposed to push it, it wouldn't be a button."
Message 8 of 18
(2,550 Views)

This did indeed fix it, thank you very much paul!

0 Kudos
Message 9 of 18
(2,520 Views)

@paul_cardinale wrote:

This fixes it.


What is it?


"Should be" isn't "Is" -Jay
0 Kudos
Message 10 of 18
(2,482 Views)