I have a ListBox on a form, say List1, Sorted = Yes, MultiSelect = 2

List1.AddItem "Alpha"
List1.AddItem "Bravo"
List1.AddItem "Charlie"
List1.AddItem "Delta"
List1.AddItem "Echo"

If I click on an item, say "Alpha", then press a letter key, say "D", the
selected item jumps to "Delta" correctly, but one second later "Alpha"
becomes highlighted again.  Upon examining selected items I see that only
"Delta" is actually selected, not "Alpha".  It is simply highlighted.  Is
this a known quirk?  Is there a workaround?

TIA
Charlie

Show quote Hide quote Looks like a bug to me; I never noticed that before.

I figured out a workaround but it's such a bunch of rigamarole I may not use
it.

It seems that the keypress-to-jump functionality sets a timer to allow for
subsequent keypresses (of the same key) to jump further down the list (within
the same character range.)  Not pressing any keys for just shy of two seconds
kills the timer.  That's when the screen gets incorrectly refreshed.  It may
be a Windows problem, not a ListBox problem, because
minimizing-then-maximizing or dragging another window over the ListBox window
erases the highlight.

I used the KeyPress event to set my own timer (code I probably got here) to
refresh the ListBox and clear the phantom highlighted row.  It flashes
momentarily (Application.ScreenUpdating didn't help) but it was the best I
could do.  I tried shortening my timer but if it fires before the keyjump
timer then it's useless. So far 1800 ms (1.8 sec) works ok.

The problem is that anytime I try something funky like this it backfires.  I
wondered what would happen if I exited the form or app before the timer
fired?  I saved my project first, as always, then clicked away.  Sure enough,
I crashed the IDE.  The compiled exe didn't seem to have a problem though. 
Still, I don't know if I'm going to use the fix or not...  Then again, broken
apps can be job security.  :)

'(in a standard module)
'
Public Declare Function SetTimer Lib "User32" ( _
        ByVal hWnd As Long, _
        ByVal nIDEvent As Long, _
        ByVal uElapse As Long, _
        ByVal lpTimerFunc As Long) As Long
'
Public Declare Function KillTimer Lib "User32" ( _
        ByVal hWnd As Long, _
        ByVal nIDEvent As Long) As Long
'
Public TimerID As Long
'
Public Sub StartTimer()
'
    On Error Resume Next
    TimerID = SetTimer(0, 0, 1800, AddressOf TimerProc)
'
End Sub
Public Sub EndTimer()
'
    On Error Resume Next
    KillTimer 0, TimerID
'
End Sub
Public Sub TimerProc(ByVal hWnd As Long, ByVal uMsg As Long, ByVal nIDEvent
As Long, _
  ByVal dwTimer As Long)
'
    frmSelectItems.lstItems.Refresh
    EndTimer
'
End Sub

'(in the form's module)

Private Sub lstItems_KeyPress(KeyAscii As Integer)
'
'   for the benefit of multiple key presses stop and restart the timer
'
    If KeyAscii >= 32 And KeyAscii <= 126 Then
        EndTimer
        StartTimer
      End If
'
End Sub



Show quoteHide quote

even simpler: I turned off the Sorted property and sorted the list myself. 
That solved it.

Show quoteHide quote

You will see similar nonsense in the VB6 IDE Project Window.
This is so that MS can provide fixes in a paid for newer version.
That's how the Windows OS has evolved!
Instead of a service pack to fix Vista, we have to pay for Windows 7.
Write your congressman or woman.
Power to the people.

Show quoteHide quote

It doesn't surprise me.

P.S. My Congresswoman is about as useless as t... nevermind

Show quoteHide quote

And tinfoil hats for all!

I don't see them on Amazon, so where can I buy them and how much?


Show quoteHide quote

Bee wrote:
http://www.google.com/products?q=tinfoil+hat  -  HTH!

It'll be even worse when Micro$oft have persuaded everyone to enter their
brave new world of the future, the world of rented software where users pay
by the hour or by the document. And it'll be even worse still if Micro$oft's
wet dream comes true, rented operating systems :-)

Mike

Looks like we've come full circle back to the old "Big Blue" (IBM) mainframe
concept.


Show quoteHide quote

It'll be even worse when Micro$oft have persuaded everyone to enter their
brave new world of the future, the world of rented software where users pay
by the hour or by the document. And it'll be even worse still if Micro$oft's
wet dream comes true, rented operating systems :-)

Mike

Problem with syntax
Scrollbars on Textbox -- how can I hide them?
The Myth of Visual Basic Migration / Upgrade
Error Message Help
Write in C
global On Error Goto ?
Excel Library in VB 2008 on 64-bit OS installation
Get My Pictures Back
MSCHRT20.ocx can no longer be used on web pages after security upd
Q re Dir$