Everything search: no effect
Moderators: Hacker, petermad, Stefan2, white
I read all postings about Everything because I use it since years.Lefteous wrote:2Horst.EppWell - no. Some users inclusing me reported that it doesn't work at all - reason unknown. Maybe YOU should read this thread first.If you read the thread above you should already know
It works with TC 9.0 beta 2 installation without problems for me and many others.
You would know if you also read all postings about it. It looks like you didn't.
If you don't like it just don't use it.
No one forces you to set the Everything option in TC
You and I may know that this is a bug forum.Lefteous wrote:2Horst.Epp
You might have noticed that this is the bug forum. If you have nothing to contribute regarding the problems just stop telling people that it works for you.
But not all questions from some users are about bugs and so my answers.
Normally I try to help users with their problems and questions if I can
but sometimes there must be also some additional comments.
Thats my style and you have to live with it as I with yours.
You are free to ignore my postings.
-
ghisler(Author)
- Site Admin
- Posts: 50550
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Sadly the Everything SDK does not have any functions to access the size/date/time fields from the beta.Perhaps users could indicate with an INI option that they are using the Everything beta until a better option becomes available?
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
I'll make an request to the Author to add thisghisler(Author) wrote:Sadly the Everything SDK does not have any functions to access the size/date/time fields from the beta.Perhaps users could indicate with an INI option that they are using the Everything beta until a better option becomes available?
Although some of you have reached this conclusion already, I'd like to confirm these findings and report the issues I described earlier as solved.
Setup: TC9b2x64 + Everything x64 1.4.0.713beta, both running elevated.
In beta2, searching with Everything works properly, and it probably already did in beta1.
The thing is I tried to do a search that was very non-specific, because I thought the difference would be best observed in that case. This is, in fact, NOT at all the case, because the processing of a large amount of files from an Everything-powered search result turns out to take more time than searching through the internal routine (at least for my setup with an SSD). However, specific search operations, i.e. those generating only few results to process by TC, are VERY fast when using Everything. This, at first, is a bit confusing, because Everything itself is pretty much instant with such non-specific results, too. Perhaps there is some performance to be gained there in TC as well.
Setup: TC9b2x64 + Everything x64 1.4.0.713beta, both running elevated.
In beta2, searching with Everything works properly, and it probably already did in beta1.
The thing is I tried to do a search that was very non-specific, because I thought the difference would be best observed in that case. This is, in fact, NOT at all the case, because the processing of a large amount of files from an Everything-powered search result turns out to take more time than searching through the internal routine (at least for my setup with an SSD). However, specific search operations, i.e. those generating only few results to process by TC, are VERY fast when using Everything. This, at first, is a bit confusing, because Everything itself is pretty much instant with such non-specific results, too. Perhaps there is some performance to be gained there in TC as well.
Unfortunately TC has to get the size and date/time info for every filename delivered from Everything. Such info is currently not available in the SDK used by TC.Guillaume wrote:Although some of you have reached this conclusion already, I'd like to confirm these findings and report the issues I described earlier as solved.
Setup: TC9b2x64 + Everything x64 1.4.0.713beta, both running elevated.
In beta2, searching with Everything works properly, and it probably already did in beta1.
The thing is I tried to do a search that was very non-specific, because I thought the difference would be best observed in that case. This is, in fact, NOT at all the case, because the processing of a large amount of files from an Everything-powered search result turns out to take more time than searching through the internal routine (at least for my setup with an SSD). However, specific search operations, i.e. those generating only few results to process by TC, are VERY fast when using Everything. This, at first, is a bit confusing, because Everything itself is pretty much instant with such non-specific results, too. Perhaps there is some performance to be gained there in TC as well.
Everything itself has this information indexed and is therefore almost instant delivering the full info if used by its own GUI.
Yes, I did read that in previous posts, however I only understand this to a certain degree: without any filters concerning size or date selected (as per default), and since the file size/date is NOT shown in the search results (not even when "Feed to listbox" is chosen), I do not see why this can't be circumvented altogether for standard searches. I might miss something here, please tell me if so.Horst.Epp wrote:Unfortunately TC has to get the size and date/time info for every filename delivered from Everything. Such info is currently not available in the SDK used by TC.Guillaume wrote:Although some of you have reached this conclusion already, I'd like to confirm these findings and report the issues I described earlier as solved.
Setup: TC9b2x64 + Everything x64 1.4.0.713beta, both running elevated.
In beta2, searching with Everything works properly, and it probably already did in beta1.
The thing is I tried to do a search that was very non-specific, because I thought the difference would be best observed in that case. This is, in fact, NOT at all the case, because the processing of a large amount of files from an Everything-powered search result turns out to take more time than searching through the internal routine (at least for my setup with an SSD). However, specific search operations, i.e. those generating only few results to process by TC, are VERY fast when using Everything. This, at first, is a bit confusing, because Everything itself is pretty much instant with such non-specific results, too. Perhaps there is some performance to be gained there in TC as well.
Everything itself has this information indexed and is therefore almost instant delivering the full info if used by its own GUI.
P.S. I seem to have missed a reply by Ghisler that was directed to me, because my name wasn't in above the quote, sorry about that.
2Guillaume
I think I answered this here.
In short: TC needs this attributes, because this is how a search works in TC. Otherwise you would have the results from Everything, but need to do another "session" of disc access afterwards.
You can e.g. already see the file time stamp and the size in the search results when marking a file, so they are needed already there.
I think I answered this here.
In short: TC needs this attributes, because this is how a search works in TC. Otherwise you would have the results from Everything, but need to do another "session" of disc access afterwards.
You can e.g. already see the file time stamp and the size in the search results when marking a file, so they are needed already there.
TC plugins: PCREsearch and RegXtract
Sorry, I was reading up and seem to have missed a page of the topic (I hate it when people do thatmilo1012 wrote:2Guillaume
I think I answered this here.
In short: TC needs this attributes, because this is how a search works in TC. Otherwise you would have the results from Everything, but need to do another "session" of disc access afterwards.
You can e.g. already see the file time stamp and the size in the search results when marking a file, so they are needed already there.
). All is clear(er) now, however I see only minor advantages for the current way of gathering the attributes during the search, compared to just gathering these details upon selecting a file (so postponing this to when it actually comes of use). Of course, IF the Everything SDK will eventually include passing through file sizes and modification dates, changing the behavior would only make sense if it also sped up the internal TC search routine (without Everything). I do realize, however, that this is a complete overhaul of the inner workings, so it's up to ghisler if he thinks so, too. Thanks for clearing it up!P.S. My 42nd post and there's not even an answer in it!
