bug in structure autogrowLV2014

[Yamaeda]

Unless i'm completely mistaken, any structure with autogrow active should grow as needed to accomodate all objects inside it.

If you have a structure inside without autogrow (i tested with Case and In place) it doesn't trigger the outer structures Auto grow! If you disable and enable the autogrow it resizes. Enabling Auto grow on the inner structure always caused the outer structure to grow as needed.

So, an inner structure without Auto grow doesn't trigger outer structures Auto grow!

Now, is this enough as a bug report or is something else needed to poke NI?

/Y

[RavensFan]

Do you think this behavior is different than it was in other LabVIEW versions?  I've always used autogrow so I never would have stumbled across this before.  I'll have to experiment when I get a chance.

[Yamaeda]

---

@RavensFan wrote:

Do you think this behavior is different than it was in other LabVIEW versions?  I've always used autogrow so I never would have stumbled across this before.  I'll have to experiment when I get a chance.

---

Different or not, it's a bug. The structure with Autogrow should grow regardless of the settings on the objects inside it.

/Y

[billko]

I would almost say this is working as intended.  It knows that you want the stuff inside to be accommodated, but it has no idea what you want to do outside of it.  I was going to say that I prefer this behavior, but I think you're saying that it runs over stuff outside of it and stuff gets hidden that way?  (I have no idea because that's one of the first things I turn off.)

Maybe NI is afraid autogrow, if unchecked in its iterations, might cause a chain reaction that would destroy the universe!  😉

[johnsold]

"Maybe NI is afraid autogrow, if unchecked in its iterations, might cause a chain reaction that would destroy the universe!  "

No, It will not do that but it might push all the pixels off the edge of the monitor being used.

Lynn

[RavensFan]

Just played with it.  I'd say working as intended and not a bug.

One thing to keep in mind is that items inside are the innermost structure are a part of that diagram.  They are not part of the diagram of the outer structure.  Only the inner structure itself is a part of the outer structure.

If I turned off auto-grow on the inner structure (which I would never do personally because it can hide code), it is to hide code on the inner structure.  If I leave auto-grow on the outer structure on, it is because I don't want it to hide code.  I don't want something that is inside the inner most structure that I want hidden to somehow affect the outermost structure.  How can you logically have something hidden on the inside structure become unhidden or having an effect on an outer structure?

[Yamaeda]

[natasftw]

---

RavensFan wrote:

One thing to keep in mind is that items inside are the innermost structure are a part of that diagram.  They are not part of the diagram of the outer structure.  Only the inner structure itself is a part of the outer structure.

---

I'd tend to side with Yamaeda on this one.  Following your idea, the inner structure is part of the outer structure following the same idea you've got there.  Let's say I've got a case structure inside a case structure (just to show this behavior).  If the inner case structure is set to not auto-grow, I'd expect anything I put inside this structure to not grow the inner case structure.  It'd follow the outer case structure wouldn't grow as well.  However, what happens when I put something inside the outer case structure here rather than the inner case structure?  I'd expect the inner case structure to be irrelevant.  It's no different at this point than any other code in the outer case structure.  If what I move into the outer case structure (NOT the inner case structure) is larger than the structure, I'd expect it to take the setting for the outer case structure and grow or not appropriately.

How does it make sense for code I add to the outer structure to rely upon a setting for the inner structure?  From a logical standpoint, it's no different than choosing a comma delimiter instead of a tab delimiter in reading a spreadsheet file changing the behavior of the outer loop's growing.  In both cases, it's a setting for something the outer loop contains.  It shouldn't dictate the outer loop's behavior.

[RavensFan]

Thanks for the picture.  That more clearly explains what you are saying.  I was thinking of a variation where you had something in the inner most structure where if you moved that beyond the boundaries, it was not autogrowing the inner structure (which it shouldn't because you turned it off), but you were expecting it to change the outer structure's boundaries because you have autogrow turned on there.

I didn't realize that you were trying to drag the borders of the inner structure beyond the outer.

I duplicated your image and tried the steps you are showing.  I agree with you now that something seems buggy about that.

For grins, I decided to drop another node.  First in just the outer loop, then later in the inner structure as well.  I found in either situation, the dropping of the code caused the autogrow of the outer structure to kick in.

So if this is a bug, (and I don't know if this happens on versions before 2014),  it is that the dragging of the border of the non-autogrow structure beyond the autogrow structure is not immediately causing the outer structure to auto grow.  It is a delayed action that happens when something else causes a recalculation (?, redraw?, recompile ??, not sure of best term) of the layout of the outer structure.

In conclusion, I change my mind and I agree this is a bug.

[billko]

---

@RavensFan wrote:

Thanks for the picture.  That more clearly explains what you are saying.  I was thinking of a variation where you had something in the inner most structure where if you moved that beyond the boundaries, it was not autogrowing the inner structure (which it shouldn't because you turned it off), but you were expecting it to change the outer structure's boundaries because you have autogrow turned on there.

I didn't realize that you were trying to drag the borders of the inner structure beyond the outer.

I duplicated your image and tried the steps you are showing.  I agree with you now that something seems buggy about that.

For grins, I decided to drop another node.  First in just the outer loop, then later in the inner structure as well.  I found in either situation, the dropping of the code caused the autogrow of the outer structure to kick in.

So if this is a bug, (and I don't know if this happens on versions before 2014),  it is that the dragging of the border of the non-autogrow structure beyond the autogrow structure is not immediately causing the outer structure to auto grow.  It is a delayed action that happens when something else causes a recalculation (?, redraw?, recompile ??, not sure of best term) of the layout of the outer structure.

In conclusion, I change my mind and I agree this is a bug.

---

I definitely agree also, now that I look at the picture.