LV 8.2 mouse behaviour oddities and annoyances ...

[tst]

---

@Darren wrote:

Someone upthread mentioned the problem of losing your grab handles, i.e. having them get "locked" to a particular object.  I have seen this behavior off and on since LabVIEW 7.0, although I haven't seen it in 8.20...yet.  Anyway, instead of searching through your VIs for the "locked" object, there's an easier (albeit very strange) way to fix it...just drop a "Format Into String" function from the String palette, then delete it.  You'll get your grab handles back.  Works every time.

---

Or, for an even simpler solution - just undo. That fixes it as well. If you don't want to undo something important, then move an object and then undo. Of course, with the resizing window bug, that is not always fun.

[NathanT]

Can you tell me how to reproduce the behavior of loosing the grad handles?  I tried continually resizing an array and other controls on the FP, but could not reproduce what I think you all are describing.  An example VI that shows this, or some steps to reproduce would be great.

Thanks,

Nathan

[Jaegen]

---

@NathanT wrote:
Can you tell me how to reproduce the behavior of loosing the grad handles?  I tried continually resizing an array and other controls on the FP, but could not reproduce what I think you all are describing.  An example VI that shows this, or some steps to reproduce would be great.

Thanks,

Nathan

---

Believe me, I've tried to reproduce it as well, with no luck (that, of course, is part of what makes this an annoying bug).  I usually see it with a fair number of VIs open, and I think it happens after switching windows, but that's about all I can offer.  Also, I think it can happen with objects on both the BD and the FP.  Perhaps it happens if an object is "active" (i.e. it's grab handles are visible) and the user Alt-Tabs to another window, rather than moving the mouse out of the object?  (Sorry, can't test that right now)

Jaegen

[JeffBoettcher]

Yeah, unfortunately that's the nature of some bugs.  Sometimes the mentality is that if a bug is "not reproducible" then it's not worth worrying about.  I like to think of it more in terms of every bug being reproducible, but sometimes the set of steps to reproduce it is so long / complicated / obscure that we never figure it out.

Regardless, even if it's "not reproducible", it still may be a bug, and therefore worth reporting or at least discussing, it just makes it a lot more difficult for us to figure out the cause and ultimately fix.