How do I turn off Auto Grow for all structures in memory?

[RavensFan]

---

@bmihura wrote:

Maybe we're doing something fundamentally different that allows your code to expand beyond the bounds of a structure that you can't see, whereas my code does not expand anywhere without me knowing about it.

---

If you've been able to structure your code that adding code isn't disappearing past the boundaries of the structure, then it won't even matter if you have Autogrow turned on because it won't need to grow the boundaries.

[QFang]

Sorry for the thread resurrect, but, the one valid case I can think of is if you are inheriting a huge mess to refactor, at least in my case, the top level VI is so large (read: no flow, no structure, no modules) that moving things around and cleaning up is super slow, and moving over structure boundaries is super slow because it starts trying to resize etc. 

[billko]

---

@QFang wrote:

Sorry for the thread resurrect, but, the one valid case I can think of is if you are inheriting a huge mess to refactor, at least in my case, the top level VI is so large (read: no flow, no structure, no modules) that moving things around and cleaning up is super slow, and moving over structure boundaries is super slow because it starts trying to resize etc. 

---

I've inherited code where the developer loved to cram as much code into nested structures with the borders of the inner structure touching the border of the outside one.  One little move of a node and all of a sudden the block diagram explodes as the structure walls run away from each other.  THAT's when I hate auto-grow.  😉

[Darren]

One of the many steps of Nattification is turning off auto-grow on structures. My original plugin operates on a per-VI basis, but Dani posted a tool on that page that will Nattify all the VIs in a project.

[QFang]

Thanks! These are great resources!!