LabVIEW
Using Arrow Keys cause my block diagram to grow.
Solved!
When it happens with a VI, does it help if you manually resize it once?
It seems to be some kind of weird mismatch to objects in the diagram and the diagram. A manual resize might be all that's needed to fix it. If the trick works, you can make a script that does this automatically.
The next step regardless the result would be to post some VI's that have this problem.
Search LabVIEW like a graph! 
wrote:
I did the block diagram clean up. It made my block diagram about 10 times bigger than it was before I started. I cleaned the diagram back to it original size and now it is happy. The only thing I did was convert the code from 2016 to 2017. I guess in 2017 the block diagram didn't like all of the over lapping of things in the different layers of the cases. The block diagram now looks exactly like it did before I started but it doesn't grow. I guess it just needed a reset.
Don't forget to mark YOUR post as the solution so anyone else who might have this issue can benefit from your hard labor. 🙂
@iannicholson wrote:
I'm now running into this, and it's maddening!!! Every time I use the arrow keys, my entire diagram "grows" about 16 pixels (this can be reverted by using "Undo"). I noticed it does the same thing if I use any right-click menu option; however, "Undo" does *not* have any effect in this scenario.
This happens on only one diagram so far, and it's a large VI so it would take me *days* to fix the damage I expect the cleanup feature to cause. I don't have that kind of time available!
I am using several Shortcut Menu plugins; I'll look through those to see if something might be going crazy...
HELP!!!
I guess it's too late to say, "Don't make huge VIs"?
This is what my main.vi usually looks like:
But if I didn't encapsulate the loops into their own subVIs - and I don't think most people do that, really - I'd probably be pressed to fit it all into one screen. I'd probably need to scroll vertically a little bit. If you had a bunch of acquisition loops, it could get hairy. In fact, it was only fairly recently that I started doing it, and it was all Ben's fault. He posted something very similar in the Channels discussion, and once I saw how neatly it wrapped everything up, I couldn't go back.
@iannicholson wrote:
@billko wrote:
This is what my main.vi usually looks like:
...
But if I didn't encapsulate the loops into their own subVIs - and I don't think most people do that, really - I'd probably be pressed to fit it all into one screen. I'd probably need to scroll vertically a little bit. If you had a bunch of acquisition loops, it could get hairy. In fact, it was only fairly recently that I started doing it, and it was all Ben's fault. He posted something very similar in the Channels discussion, and once I saw how neatly it wrapped everything up, I couldn't go back.
Bill,
I have started converting some of our applications to that model. The VI I'm referring to is over 10 years old now, and was written as I was learning LabVIEW. I see things every time I look at it that I should have done differently...
EDIT: And yes, one of the directives I was given in the beginning was to keep everything in one screen-space to minimize scrolling. Our former engineer's code had pages and pages of scrolling (vertically AND horizontally!!!); I guess it was fine for him because he was the only developer. But the boss told me to start from scratch and forbade me from using any existing spaghetti code.
LOL - I cringe every time I have to go back in time like that. It's never pretty. 😉 I wish I could help with your current issue, though. 😞
@iannicholson wrote:
This happens on only one diagram so far, and it's a large VI so it would take me *days* to fix the damage I expect the cleanup feature to cause. I don't have that kind of time available!
You can do partial diagram cleanup (last time I checked, never actually used it). Simply select a suspicious part, and it will only cleanup that part. And you can mark diagrams (e.g. the inside of structures) to skip cleanup actions ("Exclude from diagram cleanup").
So you can be selective in what to cleanup and what not to cleanup...
Of course you can cleanup everything, and if it helps revert. Cleanup 50%, and if it helps, revert. And so on, until you found the real problem(s).
I wonder if scripting can be used to detect this problem. And fix it... Hard to say without at least a few reproducible examples (in other words, post some code).
