L
Luc
More than a year ago, not long after Vista came out, I posted a description
of a bug here in this group (descriptions of three issues actually, this is
only about the third - I've learned to live with the other two).
A bit to my surprise, this issue has not been fixed in SP1.
It's the third bug in this post:
Message-ID: <[email protected]> or
http://groups.google.co.uk/group/microsoft.public.windows.vista.general/msg/a0c4aeb4f5a7817f
There was somewhat of a discussion about it later, the fact that it affects
only folders on NTFS formatted disks was discovered in the course of that
discussion.
A walkthrough showing how to recreate the problem using nothing but
explorer and cmd.exe can be found in Message-ID:
<[email protected]>
To recapitulate: using Shift+Click to select a range of files in explorer,
on a volume that is NTFS formatted, creates a risk that whatever you
selected the files for will be applied to more files than you intended.
The problem did not occur with FAT volumes (at least not last year, I don't
have any to test it with right now.)
When events take place in this order:
1) You click (select) a file somewhere near the start of a folder.
2) An application (or you, in another window) creates one or more new
subfolders in that folder. New files will also do, if they precede the
file you selected in alphabetical order.
3) You shift-click a second file further in the folder, to expand your
selection to a range.
If this happens, Explorer will select more files than you told it to.
It may even go unnoticed in large directories, if the error takes place in
a part that's scrolled out of view.
What causes it is the fact that folders on NTFS are kept sorted in explorer
(folders on FAT are not, you have to refresh them).
New files and folders on NTFS appear immediately at their correct
alphabetic position. When you select a range by click and shift-click
however, explorer remembers the _position_ in the alphabetical list of the
first object you select, instead of its identity.
If the list is changed between click and shift-click, it takes the wrong
object as "first".
of a bug here in this group (descriptions of three issues actually, this is
only about the third - I've learned to live with the other two).
A bit to my surprise, this issue has not been fixed in SP1.
It's the third bug in this post:
Message-ID: <[email protected]> or
http://groups.google.co.uk/group/microsoft.public.windows.vista.general/msg/a0c4aeb4f5a7817f
There was somewhat of a discussion about it later, the fact that it affects
only folders on NTFS formatted disks was discovered in the course of that
discussion.
A walkthrough showing how to recreate the problem using nothing but
explorer and cmd.exe can be found in Message-ID:
<[email protected]>
To recapitulate: using Shift+Click to select a range of files in explorer,
on a volume that is NTFS formatted, creates a risk that whatever you
selected the files for will be applied to more files than you intended.
The problem did not occur with FAT volumes (at least not last year, I don't
have any to test it with right now.)
When events take place in this order:
1) You click (select) a file somewhere near the start of a folder.
2) An application (or you, in another window) creates one or more new
subfolders in that folder. New files will also do, if they precede the
file you selected in alphabetical order.
3) You shift-click a second file further in the folder, to expand your
selection to a range.
If this happens, Explorer will select more files than you told it to.
It may even go unnoticed in large directories, if the error takes place in
a part that's scrolled out of view.
What causes it is the fact that folders on NTFS are kept sorted in explorer
(folders on FAT are not, you have to refresh them).
New files and folders on NTFS appear immediately at their correct
alphabetic position. When you select a range by click and shift-click
however, explorer remembers the _position_ in the alphabetical list of the
first object you select, instead of its identity.
If the list is changed between click and shift-click, it takes the wrong
object as "first".