LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Add a Drop down menu / Combo Box into a specified cell of a multi column lsit box

Your solution is based on a completely different premise, so you're trying to compare a watermelon to a peach. Your premise is that each element is a dropdown. Well, this is a trivial and obvious solution - use an array of dropdowns. The original premise is to use a multicolumn listbox or table that would behave like a DataGrid in which specific columns (and only those columns) are dropdowns. Totally different beast.
0 Kudos
Message 11 of 19
(4,959 Views)

Like I said the other solution posted on this thread takes you through gyrations..... Attached you will find a simpler way of getting this done...Yes, 1 out of many ways to do this....

 

Basically, single click to edit the Table cell, double click to use the pop down menu... You can edit as you see fit cus it rough cut.... go ahead comment away, I've seen this done b4, yea its not new...

0 Kudos
Message 12 of 19
(4,942 Views)
What exactly do you consider a "gyration"? The VI in reply #6 suffers from relying on constants rather than picking up this information directly from the control. Other than that I see no "gyrations". The solution that Eugen had started to put together seems fairly straightforward to me as well, as it relies on the control itself.
0 Kudos
Message 13 of 19
(4,914 Views)

Here's a sample, NI "style" of coding... I have to check the rule book. And this is not all either. I do believe a LAVA contributor mentioned "complex" or to that liking

Message Edited by richjoh on 11-10-2008 10:44 AM
0 Kudos
Message 14 of 19
(4,905 Views)

 

FYI

 

There is an invoke node method available to help translate clicks to cells (which I am not sure would help here but it's worth sharing Smiley Wink )

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 15 of 19
(4,901 Views)

Ben wrote:

There is an invoke node method available to help translate clicks to cells (which I am not sure would help here but it's worth sharing Smiley Wink )


Indeed, and that's exactly what I meant in my statement 


The VI in reply #6 suffers from relying on constants rather than picking up this information directly from the control.
However, the VI that Eugen had started to put together still seems fairly straightforward to me, as it does just that, and is a better starting solution that the one posted in reply # 8, since using the Edit Pos places the dropdown's top-left corner where the user double-clicked, which is in the wrong place. Also, requiring the user to double-click seems counterintuitive to me. But perhaps I'm just old-fashioned.
0 Kudos
Message 16 of 19
(4,890 Views)

This is precisely what I've already done (use Invoke node), the VI is posted above, see the attached pic of the BD. Open it and have a look at the Invoke node. Not the only way to do either...

 

 

0 Kudos
Message 17 of 19
(4,879 Views)

Ya the reply from #6 seems foolish stuff. But at the end I still prefer TSPopup.Lookup.vi, contributed from LAVA. Thanks to JDave.

http://forums.lavag.org/Type-Sensitive-Popup-file105.html

 

By TSPopup.Lookup.vi, just feed in current coordinate and control reference, and u get what u wanted. You need not care about the "constant" coordinate, as where the control is located.

 

Just to share out some good stuff here. Feel free to shoot me.  🙂

Message 18 of 19
(4,864 Views)

hi, 

 

i modified yours with more flexible, no need manual offset when the table is moved

0 Kudos
Message 19 of 19
(2,810 Views)