QuickSearch started with Alt-Letter bad search
Moderators: Hacker, petermad, Stefan2, white
QuickSearch started with Alt-Letter bad search
If I have the files like this:
Image: http://i49.tinypic.com/5orrsl.png
and I have Quick Search configured with Alt-Letters then when I Quick Search the file named cd.txt by typing
Alt-"c" then "d" then "." (dot)
Total Commander doesn't move from the first file on the screen (cd1.txt)
Expected behaviour: to move to the cd.txt
I zipped the directory with which this can be repeated:
http://www.mediafire.com/file/7zdyy131h5xtm21/tcsample.zip
The example is made to be small, I noticed this in much bigger directories where the file I needed was not even shown in the visible region. Thanks in advance.
Image: http://i49.tinypic.com/5orrsl.png
and I have Quick Search configured with Alt-Letters then when I Quick Search the file named cd.txt by typing
Alt-"c" then "d" then "." (dot)
Total Commander doesn't move from the first file on the screen (cd1.txt)
Expected behaviour: to move to the cd.txt
I zipped the directory with which this can be repeated:
http://www.mediafire.com/file/7zdyy131h5xtm21/tcsample.zip
The example is made to be small, I noticed this in much bigger directories where the file I needed was not even shown in the visible region. Thanks in advance.
Last edited by serjayes on 2012-07-30, 15:00 UTC, edited 3 times in total.
(user licence #64081)
I typed "c" "d" "." (I fixed the parent post to make it clear) meaning I want the file "cd.txt" which is somewhere deep down in the list, not the file cd1.txt which is the one on which I started.umbra wrote:What is the bug? In your example, you typed Alt+"cd", which means, you want all files that start with "cd". Plus you set the sorting to sort the suitable results by date. And TC did it exactly as requested. Why do you think it should do something different?
Sorting by date is irrelevant, except that when there are more files with the same start, I expect to get the first one according to the date. But I want to reach cd.txt and I can't.
(user licence #64081)
- Balderstrom
- Power Member
- Posts: 2148
- Joined: 2005-10-11, 10:10 UTC
If you don't use exact match then you don't need to preface QuickSearches with an asterix * when you want to match part of a filename.
Given the Files:
ExampleFile001.txt
TopicLabel002.txt
Without Exact name match, you could type
a (or alt-a, if using the alt-key modifier for search)
The result would be to jump to the first file that has the letter "a" somewhere in it's name. If you typed 'a' (alt-a) again, the cursor would jump to the next file that has an 'a'... Now if instead you had a file that contained 2 consecutive a's in it's name, then the cursor would jump to that file.
If you set exact match, instead you would do:
*a (Would match both files, OR)
??a (Would only match letter-letter-A)
Given the Files:
ExampleFile001.txt
TopicLabel002.txt
Without Exact name match, you could type
a (or alt-a, if using the alt-key modifier for search)
The result would be to jump to the first file that has the letter "a" somewhere in it's name. If you typed 'a' (alt-a) again, the cursor would jump to the next file that has an 'a'... Now if instead you had a file that contained 2 consecutive a's in it's name, then the cursor would jump to that file.
If you set exact match, instead you would do:
*a (Would match both files, OR)
??a (Would only match letter-letter-A)
*BLINK* TC9 Added WM_COPYDATA and WM_USER queries for scripting.
There are several such scenarios, for example:serjayes wrote:What are the scenarios when somebody doesn't want to get to the file which is exact match of what he types up to some point?
1. people don't know the exact name of a file
2. people want to see the searched file in a context of other similarly named files
3. file's name is too long to type - it's faster to write a first few characters and then use up/down keys or mouse (I think, this might be the most usual reason)
Windows 10 Pro x64, Windows 11 Pro x64