Listbox bug?

VFP 8, 9 in XP Pro

Given a standard listbox with about 10 items shown and set to
multiselect, should a click and drag within the listbox select
the range of items overwhich the drag took place? It appears
that this is the desired behavior, however, one or more items
in the list always end up not selected after performing such
a selection. It's almost as if an event or interrupt takes
place during the drag and VFP does not register the items as
selected when that interrupt was happening. Clicking the first
desired item, then shift-clicking the last one works fine,
but dragging a range of items is spotty. Is this a known
bug?

-- TRW
_______________________________________
t i m . w i t o r t
_______________________________________

Olaf
Tue Jun 26 03:58:43 CDT 2007

I see the same behavour when moving the mouse fast,
so it does not mouseover all items.
I'd say it's by design, as the selection seems
to be done through the native mouseover or
mouseenter event.

I'd say if you want a better behaviour, you
need to implement something drawing a frame
like it's solved in windows explorer...

Bye, Olaf.

tim_witort
Tue Jun 26 11:15:34 CDT 2007

Olaf Doschke seemed to utter in news:euqeVE9tHHA.1208@TK2MSFTNGP05.phx.gbl:

> I see the same behavour when moving the mouse fast,
> so it does not mouseover all items.
> I'd say it's by design, as the selection seems
> to be done through the native mouseover or
> mouseenter event.

I would say that it's *due to* design, not *by* design.
I don't think the intention was for random items to end up
not selected.

> I'd say if you want a better behaviour, you
> need to implement something drawing a frame
> like it's solved in windows explorer...

Good idea. I'm not sure I'm that committed to fixing the
behavior though. I'll just hope that the users don't
try to drag to select items and get confused at the
spotty results.

-- TRW
_______________________________________
t i m . w i t o r t
_______________________________________

Dan
Tue Jun 26 14:20:04 CDT 2007

That's tied in with another listbox infelicity.

In that same listbox, turn off multiselect. Select an item and observe
.Value

Select the same item and before letting up on the mouse slide to another
item on the list. Notice that .Value changes yet neither .Valid() nor
.InteractiveChange() will fire. I consider this an outright bug but I've
been reporting it for years and it doesn't get fixed so I'm guessing it's
deep in the product.

Dan

Tim Witort wrote:
> VFP 8, 9 in XP Pro
>
> Given a standard listbox with about 10 items shown and set to
> multiselect, should a click and drag within the listbox select
> the range of items overwhich the drag took place? It appears
> that this is the desired behavior, however, one or more items
> in the list always end up not selected after performing such
> a selection. It's almost as if an event or interrupt takes
> place during the drag and VFP does not register the items as
> selected when that interrupt was happening. Clicking the first
> desired item, then shift-clicking the last one works fine,
> but dragging a range of items is spotty. Is this a known
> bug?
>
> -- TRW
> _______________________________________
> t i m . w i t o r t
> _______________________________________

tim_witort
Wed Jun 27 10:58:22 CDT 2007

Dan Freeman seemed to utter in news:#RLyAcCuHHA.736@TK2MSFTNGP06.phx.gbl:

> Tim Witort wrote:
>> VFP 8, 9 in XP Pro
>>
>> Given a standard listbox with about 10 items shown and set to
>> multiselect, should a click and drag within the listbox select
>> the range of items overwhich the drag took place? It appears
>> that this is the desired behavior, however, one or more items
>> in the list always end up not selected after performing such
>> a selection. It's almost as if an event or interrupt takes
>> place during the drag and VFP does not register the items as
>> selected when that interrupt was happening. Clicking the first
>> desired item, then shift-clicking the last one works fine,
>> but dragging a range of items is spotty. Is this a known bug?
>>
>> -- TRW

> That's tied in with another listbox infelicity.
>
> In that same listbox, turn off multiselect. Select an item and observe
> .Value
>
> Select the same item and before letting up on the mouse slide to
> another item on the list. Notice that .Value changes yet neither
> .Valid() nor .InteractiveChange() will fire. I consider this an
> outright bug but I've been reporting it for years and it doesn't get
> fixed so I'm guessing it's deep in the product.
>
> Dan
>

Woah! That's even worse behavior than the one I'm dealing with!

-- TRW
_______________________________________
t i m . w i t o r t
_______________________________________