I must have missed the "NT" before the lost. Sorry.
Message
From: delphi-bounces (AT) elists (DOT) org [mailto:delphi-bounces (AT) elists (DOT) org] Behalf
CubicDesign
Sent: Wednesday, 20 June 2007 22:26
To: Borland's Delphi Discussion List
Subject: Re: Multi select not working as expected in TFileList.
Ross Levis wrote:
That's not what I experience in Windows Explorer. I can click a file;
release mouse button; shift+click another file to select multiple files;
release mouse button. Now click and hold the mouse button down on a
selected file and it starts dragging all the files.
Yes, this is _exactly, exactly_ what I said.
*In Explorer:*
After I made a multiple selection then I release the button, then I
click (and hold the button down) the selection again, the selection is
NT lost.
*In TFileList:*
After I made a multiple selection then I release the button, then I
click (and hold the button down) the selection again, the selection IS lost.
The question is how repair this problem without modifying the original
(Borland) files because I tried to create a new custom component based
on TFileList and the problem can't be fixed in MouseUp/MouseDown?
Somebody knows if this was fixed in Delphi 2007?
Message
From: delphi-bounces (AT) elists (DOT) org [mailto:delphi-bounces (AT) elists (DOT) org]
Behalf
CubicDesign
Sent: Monday, 18 June 2007 20:41
To: Borland's Delphi Discussion List
Subject: Re: Multi select not working as expected in TFileList.
>
>
>
Doug Chamberlin wrote:
>You do need to mouse-down on the final selected item and
>then immediately start the drag operation. Isn't this standard behavior?
>>
>
>
>
I didn't used Windows Explorer in the last 10 years so I went straight
in Explorer and
1. I selected some files (shift click)
2. Then I released the click
3. I clicked again on the selection (in order to start the drag
operation) and the selection was not lost, like it is lost in TFileList.
So I don't think that TFileList has a 'standard' behavior.
Maybe I don't use Explorer, but I know that many (majority) users do.
This bug appears on the 'fixed bugs list' in Delphi 4. It looks like
somewhere on the road, between D4 and D7 it was reintroduced.
Delphi mailing list -Delphi (AT) elists (DOT) org
Delphi mailing list -Delphi (AT) elists (DOT) org
Delphi mailing list -Delphi (AT) elists (DOT) org