Block diagram corrupted by "clean up selection"

[aputman]

---

@Ben wrote:

---

---

Quoting This Old Tony, "Time travel is dangerous."

---

I love to watch This Old Tony, even though I am not a machinist.  His video editing and sense of humor are genius. 

[RavensFan]

---

@BertMcMahan wrote:

You can try the Ctrl-Alt-click and drag to shrink the diagram. It might pull in the "stuff" that got caught in the nether.

---

Thanks for the tip.  I thought I heard one time in one of the recent versions the ability to shrink the diagram was added, but never actually saw it and never heard the magic key combination.

[Ben]

---

@aputman wrote:

---

@Ben wrote:

---

---

Quoting This Old Tony, "Time travel is dangerous."

---

I love to watch This Old Tony, even though I am not a machinist.  His video editing and sense of humor are genius. 

---

Glad to read I am not alone.

I believe it was this video where he warned us about time travel.

Ben

[Kyle97330]

As for an actual method to fix the issue, have you tried VI scripting?

Open your VI by reference, traverse it for all GObjects on the block diagram, then look for any of those that have a "Position:Left" property outside the bounds allowed by an I16, and programatically assign them new locations.  It will look ugly but should at least get them all on-screen.

The GObject's Position:Left and Position:Top properties are I32, so it could work...

[paul_cardinale]

---

@billko wrote:

I think ctrl + z gets taken off the table the moment you save the VI, even if it is still open and in memory - a BIG complaint of mine!

---

They fixed that a few versions ago.  It now works after save.

[grahamt8887]

Thanks for all the suggestions.

In the end I just reverted to my backup from last week and redid everything I had done since, which always has the benefits of making it better.

The block diagram extended past the I16 range in both +ve and -ve directions...it is totally kaput. I can open the BD, but the moment I click anything, like change to view a different case, it crashes and shows me a blank BD.

The traverse for GObjects is a nice idea, and I started down that route but decided it may take even longer than redoing my code.

I can't remember what happened with ctrl-z - but anyway I had to restart labview pretty shortly afterwards (after it crashed), so I think the undo memory is lost then anyway?

Graham

[Yamaeda]

Yes the Clean Up function often blows up the diagram, and Clean selection can be even worse. However, one can sometimes fix/help the other (but Always keep your fingers on ctrl+z). In this case, how do it react if you do a Clean Up on the full diagram?

/Y