Bug when updating a type def Enum

[Samdub19]

Hello everyone,

I have been experiencing a weird bug for a while now in the main VI of my program: after adding conditions to an Enum (by updating the type def), the main VI in which this Enum is used (the Enum defines the While loop conditions as shown in the image) is completely shifted, and I end up having diagonal cables and shifted elements in every conditions. In addition, every actions performed on the diagram shift the code to the left, and it eventually stops after few iterations. 

Have you ever encountered this bug before ? 

I am using LabVIEW 2019 32bits with Windows 10. 

Thanks in advance,

Sam

[GerdW]

Hi Sam,

---

@Samdub19 wrote:

I have been experiencing a weird bug for a while now in the main VI of my program:

---

Have you tried to edit a revision of your VI that is older then "for a while now"?

(I guess you use a SCC tool, do you?)

---

@Samdub19 wrote:

Have you ever encountered this bug before ? 

---

I have seen similar behaviour when the VIs had a (too) large block diagram.

What are the metrics of your VI?

[Yamaeda]

I've seen something similar, but never diagonal wires!

Shifted elements sounds like you add or shift Items in the middle of the Enum, that's always dangerous and requires you to be extra careful.

If the VI has been corrupted, which the diagonal wires could point to, you can try to copy the entire Block diagram to a new VI and see if it behaves better.

Source Code Control - SCC, is built for these instances, assuming you remember to check in every so often.

[paul_a_cardinale]

When editing enum typedefs, I don't make a bunch of changes, then apply.

I do "Apply Changes" after each individual change.  It's cumbersome, but it reduces headaches.

[billko]

---

@paul_a_cardinale wrote:

When editing enum typedefs, I don't make a bunch of changes, then apply.

I do "Apply Changes" after each individual change.  It's cumbersome, but it reduces headaches.

---

To expand on that, if I want to add an item to the middle, I first add it to the bottom, apply changes, and then move it and apply changes.

[Samdub19]

Hi Gerd,

Yes I use an SCC tool and we can see that this problem does not occur in an older version of VI, without really understanding why.

I will try to reduce the block diagram to see if the problem still occurs.

Thank you !

[GerdW]

Hi Sam,

---

@Samdub19 wrote:

I will try to reduce the block diagram to see if the problem still occurs.

---

What are the metrics of the VI?

Tools menu -> Profile -> VI metrics, enable statistics for diagram and look for diag width/height…

[Samdub19]

Hi Gerd,

It seems that I don't have this option in my LabVIEW 2019. Is there an other way to obtain such informations ?

Thank you.

[GerdW]

Hi Sam,

tools->profile->VI metrics is already part of the base edition IMHO:

You can show the navigation window (ctrl-shift-n) and show a screenshot of that window. Then one can compare screen/window size with diagram size:

The white background shows a FullHD screen, so the block diagram is slightly larger than the screen. (A QMH with several handler loops…)

[Bob_Schor]

My own "Rule of Thumb" (which I learned from reading, several times, Peter Blume's "LabVIEW Style Book" cover-to-cover) is to make all of my VIs fit on a standard Laptop screen.  Sometimes this involves making a parallel loop into a sub-VI taking (only) 32 x 32 pixels, but this lets you concentrate on the Top Level vi ...

Notice Gerd's picture shows his example is pretty close -- I'd call it about 1.3 x 1.3 Laptops.  We've seen some Block Diagrams that are 15 x 5 Laptops, clearly a challenge to manage (unless you have 75 monitors available).

Bob Schor