Structure resize issue.

[XM43]

Hi,

Hope you are doing great!

I have a project in which some of the older VIs are showing this visual effect where if the structures are made to resize, they overlap or overshadow other item on the block diagram. I am not sure if this is something that I unknowingly triggered somehow or if it is a possible bug/glitch.

This does not happen with any newer VIs. But I have well over 100+ VIs that all of a sudden started to act this way about 2 months ago.

Additional Information:

-This is an inherited project which was originally made in LabView 2016 and current version in use is LabView 2019.

-This did not happen when version was changed initially and everything was normal for about 8 months.

-Only some structures in a VI show this effect, not all.

-It occurs on RT and PC side VIs. Does not happens with VIs on FPGA.

-Some VIs have had about 1796 revisions.

Below are some screenshots and I am also attaching an example VI.

Normal:

Collapse:

Expand:

Is there something I can do about it? Code works fine but at times I accidentally hide pieces of code while resizing a structure which could become a problem at some point.

Thank you for reading and your time.

[billko]

It seems normal to me.  What are your expectations?  I wasn't clear on what you wanted to happen vs what actually happens, sorry.

[johntrich1971]

I also don't understand your question. How are you resizing your objects (it sounds like you're doing too much resizing). When I opened your program and used CTRL-Mouse it resized just fine - moving the objects. It sounds like you're trying to drag the edges of loops, etc. This will always hide objects or put other objects on top of the loop as shown in your pictures. 

[GerdW · Accepted solution]

HI Xonmyth,

by default LabVIEW places structures on the block diagram with automatic resizing ("Auto Grow") enabled, but you can switch off this behaviour in the LabVIEW options.

You can switch that resizing behaviour also on a "per structure" base in the right-click options of the structures: see the first note in this LabVIEW help article.

I guess you use the default setting, while that inherited project was created with auto-resizing switched off. That's why those inherited VIs show the behaviour in your images!

(I prefer that AutoGrow feature, but others might argue against it…)

[XM43]

Hi GerdW,

Thank you for your prompt response and information. I had no clue that I could turn auto sizing on and off for structures. 😬

Edit:

I think from today I can say that I prefer "Auto Grow" feature as well. Since I potential could hide a piece of code and wonder what's wrong. Since I did that quite a few times now.

[billko]

---

@XM43 wrote:

Hi GerdW,

Thank you for your prompt response and information. I had no clue that I could turn auto sizing on and off for structures. 😬

Edit:

I think from today I can say that I prefer "Auto Grow" feature as well. Since I potential could hide a piece of code and wonder what's wrong. Since I did that quite a few times now.

---

The first time your block diagram explodes when you drop something in a nested structure, you might not be so quick to adopt it.  😉

[Yamaeda]

Those structures don't have the "Auto Grow" set. Then that's expected behaviour. Some like to do old school and program without it, i tend to like when LV stops me from doing such silly things. 🙂

[johntrich1971]

---

@GerdW wrote:

HI Xonmyth,

by default LabVIEW places structures on the block diagram with automatic resizing ("Auto Grow") enabled, but you can switch off this behaviour in the LabVIEW options.

You can switch that resizing behaviour also on a "per structure" base in the right-click options of the structures: see the first note in this LabVIEW help article.

I guess you use the default setting, while that inherited project was created with auto-resizing switched off. That's why those inherited VIs show the behaviour in your images!

(I prefer that AutoGrow feature, but others might argue against it…)

---

I didn't even think about AutoGrow since I haven't found a reason for it - other than to make my block diagram get too large. I do often use its cousin, though, using the CTRL key with the mouse to grow the object in a more controlled manner.

[XM43]

@billko wrote:

It seems normal to me.  What are your expectations?  I wasn't clear on what you wanted to happen vs what actually happens, sorry.

---

I am not as experienced as you guys, I am fairly new to this. When I started using LabView, as @GerdW mentioned, I used all the default settings and those default setting were standard for me. I had no idea "Auto Grow" will be a thing that I will come across or if people turn off that option. 

I am still learning and exploring.

@johntrich1971 wrote:

How are you resizing your objects (it sounds like you're doing too much resizing). When I opened your program and used CTRL-Mouse it resized just fine - moving the objects. It sounds like you're trying to drag the edges of loops, etc. This will always hide objects or put other objects on top of the loop as shown in your pictures. 

---

I resize them as needed. If I have nested structure, I will use CTRL+Drag. If it is some structure on the outside then I will Click and Drag the edges.

Yes, I am doing a lot of resizing as I am supposed build upon the inherited project and make it more detailed, add feature to existing code and add new pieces of code. All the structures in the existing code were sized to show all the objects on the block diagram (which is what "Auto Grow" would do) and from what I remember, all the structures at one point had "Auto Grow" feature enabled by default and then I somehow accidentally turned it off. Which confused me and threw me off.

The first time your block diagram explodes when you drop something in a nested structure, you might not be so quick to adopt it.  😉

---

ummmm....I am not sure how to respond to that, sorry 😛. I am familiar with block diagram exploding when dragging items and I like it that way. This way I at least have one less variable to worry about "Hidden items".

@Yamaeda wrote:

Those structures don't have the "Auto Grow" set. Then that's expected behaviour. Some like to do old school and program without it, i tend to like when LV stops me from doing such silly things. 🙂

---

Hi Yamaeda,

Yes, you are right that's what it was. I agree with what you said! 🙂

@johntrich1971 wrote:

---

I didn't even think about AutoGrow since I haven't found a reason for it - other than to make my block diagram get too large. I do often use its cousin, though, using the CTRL key with the mouse to grow the object in a more controlled manner.

Well, from what I remember learning from LabView courses, if the block diagram gets too large, make subVIs and that is what I go by. But now I can imagine how you approach this. But at this point I am scared to go down that route.

-------------------------------------------------------------------------------------------------------------------

I am thankful for everyone's input! 🙂