Interference with Drag/Drop on MC ListBox

[CoastalMaineBird]

OK, I see no explanation for that except a LabVIEW bug.

DId you try that in LV2010 or 2011, or 2012 or what?

[tst · Accepted solution]

I would suggest using the Mouse Down event instead. Since you're not actually changing anything, it doesn't sound like the discarding part is really necessary.

---

@CoastalMaineBird wrote:

Why did you suggest rearranging the event order?  On the face of it, that should have no effect (and it didn't).

Have you had trouble before where that fixed it?

---

It was my understanding that there is some significance to the order of the events (I think it's that if you get two events at the same time, the one which is earlier in the structure will be processed first), but a) you shouldn't quote me on that and b) it probably doesn't apply to filter events, because I expect those are processed first anyway. I just thought it was worth checking.

It's also quite possible that what I'm thinking of are case structures, where the match is compared by the order of the cases, but I'm not sure about that either. In either case, it would be an implementation detail.

[tst]

---

@CoastalMaineBird wrote:

OK, I see no explanation for that except a LabVIEW bug.

DId you try that in LV2010 or 2011, or 2012 or what?

---

I tried a modification of my example in the 2013 beta and it still happens. I suggest you modify my VI to demonstrate the issue properly and then report it as a bug in a new thread.

[johnsold]

Steve,

It is possible to "defeat" the tip strip. Sort of...

Use the Property Node for the Tip Strip text. (I did not look up the exact name.) Writing an empty string to the property node make the tip strip disappear. To bring it back you need to write the text to the property node again.  So that means that at the beginning of the program you need to read the tip strips' texts and save them somewhere for restoration.

I discovered this while discussing the annoyance of tip strips which get in the way at a recent NI Developer Education Day seminar.

Lynn

[CoastalMaineBird]

Lynn, you're misunderstanding something. Look at the video.

It's not a real tip-strip.

I used the term "something like a tip strip" because it's similar in appearance and function.

But it's not the "Tip" for the MCLB.

It's something that pops up automatically when the mouse is over a cell where the text is longer than the cell width.

My "Tip" property was already empty, that property has no effect on this issue.

[johnsold]

Sorry.  I did not look at it.  I just saw the word tip strips.

Lynn

[CoastalMaineBird]

Thanks, tst.

I have added some explanation to your VI and will send this in to tech support.

It is attached for your amusement.

[CoastalMaineBird]

I would suggest using the Mouse Down event instead. Since you're not actually changing anything, it doesn't sound like the discarding part is really necessary.

Well, I've accepted your solution, tst.

I used the FILTER version due to old habits, I suppose.  It seems good practice to me, to declare that

"I handled this event, so I don't want to pass it on",

or

"I didn't handle this event, maybe somebody down the chain can handle it".

In my case there is no harm done by passing it on regardless, so that's what I'll do.

Still, it's a bug, and I've reported it.

[CoastalMaineBird]

Acknowledged by NI Tech Support as a bug.

There is a Corrective Action Request(CAR) #398003 established.