LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

multicolumn listbox double-click not caught in event structure

I'm writing a simple directory explorer utility, because I can use it, and just to give me some more experience writing LV apps. The explorer is event driven, and everything seems to work just fine EXCEPT if I double-click a directory entry in the multicolumn listbox. The event fires correctly, but the Get DblClk Row property returns -2 (indicating no row was double-clicked) regardless of where I double-click in the listbox.

I've tried creating a property node from the terminal and placing it inside the event case - didn't work. Next I tried using the event data structure control reference and creating a property node from that - didn't work. Finally, I've created a control reference from the terminal and created the property node from this reference - still doesn't work.

I'm attaching the .llb in question. The top-level .vi is called Directory Event Explorer... Any ideas?

Oh, LV7.1 and WinXP Pro.

Thanks.
0 Kudos
Message 1 of 6
(3,672 Views)
It is difficult to find the problem if you remove the block diagram from the attached example. 😞
0 Kudos
Message 2 of 6
(3,654 Views)
Since your llb has all diagrams removed, it's impossible to see what you did. The attached example does show that the double click event does return the actual row that has been double clicked. All you need is the row value of the Event Data Node.
0 Kudos
Message 3 of 6
(3,654 Views)
Oops, clicked on the wrong distribution when I saved it as a .llb file. I'm attaching the correct distro (with block diagrams included)...

Thanks.
0 Kudos
Message 4 of 6
(3,645 Views)
0 Kudos
Message 5 of 6
(3,640 Views)
I looked at the event data structure in your example and saw the Row element. The element didn't appear in the default data structure, and I somehow missed it when I was trying to determine which element would give me what I needed. I figured that the double-clicked row was probably being read by the event handler itself, and was no longer "defined" within the event, but couldn't figure out how to pass in this value. Thanks for your help.
0 Kudos
Message 6 of 6
(3,634 Views)