Listbox behaves in unexpected manner

[jlokanis]

The multi column listbox does not behave as I would expect.  This casues problems for the users of my application.  Here are the steps to reproduce:

Create a system multi-column listbox. Fill in several rows with some data.
Set the properties Active Cell and Edit Position to a row in the middle of the ones you populated.
Set the value to that same row.
Set the key focus to true.
Create a simple while loop to keep the VI running after all these setting are applied.
Run the VI. The row you set should be selected.
Use the up/down arrow keys to move to another row more than 2 rows away.
Stop the VI
Run the VI again.
Use the arrow keys to move the selection again. Instead of moving relative to the programmatically selected row that is highlighted, it will jump to the row that was (up/down) from the row you moved to right before you last stopped the VI.

Why does it do this? Why does it remember the last selection you navigated to? How can I override this so the selection I set programmatically is the one it will move relative to when the use uses the arrow keys?

Is this a bug?

[Pnt]

Looks like a bug.

Labview 8.2 has the same behavior...

[Matthew_Kelton]

Here is a workaround.  Use an event structure to handle the up and down button presses instead.  I don't see that you did anything wrong in what you posted.  It appears the control doesn't update some internal value for the arrow keys unless the user clicks on a row.  Even the Value (Signaling) property doesn't address the issue.

[Matt_W1]

If you go the event route make sure to capture the Key Repeat? event as well as Key Down? (otherwise it'll move back to it's wrong postion if you hold down the arrow key). You'll probably want to set the top left cell, to keep the current selection in view as well.

[SnowBoy111]

diverting to new question

we need to generate a double click event .

when user presses single button it should generate a dobule click event in block diagram. ,

eg. when we click a button in front panel , it should generate a double click event in the same way as we double click on an express vi to see properties or load data file . (sim arbt signal)

thanks

Hader

[RavensFan]

Don't divert the thread to a new question.

Your actual question is already located in your new thread here.

[Craig_D]

This was reported to R&D (# 4GUA4BLJ) for further investigation.  For now, the workaround that Matthew suggested using events should work the way you intended. Thanks for the feedback!

Regards,

Craig D
Applications Engineer
National Instruments

[Brett_J]

Hi,

Any update on the progress of this, I am having the same issue in LabVIEW 2009 SP1, and would prefer not to use the keyboard up/down events if possible.

Brett

[Matthew_Kelton]

I can confirm it still exists in LabVIEW 2011.  I don't see it on the known issues list.  Has this fallen through the cracks?

[jlokanis]

I'm still using the workaournd in my code.  Sure would be nice for them to fix or explain this one.