G
Guest
I have been fighting a very strange issue with a listbox.
I am using the Before doubleclick event from a worksheet to trigger a
dynamic build of a rowsource for a listbox with a .show that should wait on a
selection from the listbox to then populate the cell that was doubleclicked.
The issue is that the 2nd click of the double click is being picked up by
the listbox as a selection.
I have verified this behavior by shifting the mouse a few pixels outside of
where the listbox will showup and the event coding works as designed.
Anytime the double click is in the same screen area that the listbox shares,
the 2nd click is taken as the choice.
I tried adding a delay loop before the doublelcick event code would execute
the form.show command, but that still did not prevent the form_Click code
from running and choosing the item from the list that just happened to fall
under where the mouse was initially positioned.
I figure that forcing the box to position itself away from the double click
may work, but that is at best just a band-aid for the problem. But might be
the only workarround.
Any thoughts of what to try to get around this issue?
I am using the Before doubleclick event from a worksheet to trigger a
dynamic build of a rowsource for a listbox with a .show that should wait on a
selection from the listbox to then populate the cell that was doubleclicked.
The issue is that the 2nd click of the double click is being picked up by
the listbox as a selection.
I have verified this behavior by shifting the mouse a few pixels outside of
where the listbox will showup and the event coding works as designed.
Anytime the double click is in the same screen area that the listbox shares,
the 2nd click is taken as the choice.
I tried adding a delay loop before the doublelcick event code would execute
the form.show command, but that still did not prevent the form_Click code
from running and choosing the item from the list that just happened to fall
under where the mouse was initially positioned.
I figure that forcing the box to position itself away from the double click
may work, but that is at best just a band-aid for the problem. But might be
the only workarround.
Any thoughts of what to try to get around this issue?