multi-thread file search function
Moderators: Hacker, petermad, Stefan2, white
multi-thread file search function
hi, I am new here.
TC has been my favoriate. but one thing I don't like is that when I am searching the file, I can't do any other things.
I would assume that adding a multithread function for searching file is not that difficult, right?
TC has been my favoriate. but one thing I don't like is that when I am searching the file, I can't do any other things.
I would assume that adding a multithread function for searching file is not that difficult, right?
31 threads---
2candl
Hello, welcome on board !
• You might try a Search about that subject. You could find, in example
this topic …
and thirty others
Kind regards,
Claude
Clo

• You might try a Search about that subject. You could find, in example
this topic …
and thirty others


Claude
Clo
#31505 Traducteur Français de T•C French translator Aide en Français Tutoriels Français English Tutorials
[face=courier]On 04-06-2004 05:32:17 +0000 candl wrote:
c> I would assume that adding a multithread function for
c> searching file is not that difficult, right?
That's another long old story. As Christian said, he didn't add background search yet because of not multi-thread safe unpacker libraries:
Christian Ghisler:
"Some of the unpackers like the external unrar.dll don't
support multi-threading. Wincmd uses them when searching
inside archives. Now when you move the search to the
background and try tu unpack another RAR file, the dll
code crashes."
Well, Christian fingered unrar.dll as the root of all evil %). So I ask Eugene Roshal about multi-thread safety of unrar.dll and he told me that as far as he knew it should be multi-thread safe. Anyway, AFAIK Christian didn't reported unrar.dll multi-thread bug details to Eugene (actually, no one else did though a lot of application use unrar.dll) so Eugene just doesn't see any reasons to make investigations in that direction.
But the strange thing is a lot of other features in Commander doesn't work with archives (e.g. user menu placeholders or search results feeding to panel), but that didn't prevented Christian from implementing them once.
So I guess this is just an excuse for not implementing background search. It looks like Christian just doesn't want to add it for some reason(s) only he knew.[/face]
c> I would assume that adding a multithread function for
c> searching file is not that difficult, right?
That's another long old story. As Christian said, he didn't add background search yet because of not multi-thread safe unpacker libraries:
Christian Ghisler:
"Some of the unpackers like the external unrar.dll don't
support multi-threading. Wincmd uses them when searching
inside archives. Now when you move the search to the
background and try tu unpack another RAR file, the dll
code crashes."
Well, Christian fingered unrar.dll as the root of all evil %). So I ask Eugene Roshal about multi-thread safety of unrar.dll and he told me that as far as he knew it should be multi-thread safe. Anyway, AFAIK Christian didn't reported unrar.dll multi-thread bug details to Eugene (actually, no one else did though a lot of application use unrar.dll) so Eugene just doesn't see any reasons to make investigations in that direction.
But the strange thing is a lot of other features in Commander doesn't work with archives (e.g. user menu placeholders or search results feeding to panel), but that didn't prevented Christian from implementing them once.
So I guess this is just an excuse for not implementing background search. It looks like Christian just doesn't want to add it for some reason(s) only he knew.[/face]
[face=courier]The Protoss do NOT run from their enemies.
It is here, that we shall make our stand.[/face]
It is here, that we shall make our stand.[/face]
- ghisler(Author)
- Site Admin
- Posts: 50505
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Believe me, I really wrote a threaded version of search, but it crashed all the time when searching in archives, or worse, gave bad output without errors.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
I sometimes experience that if one TC instance is searching for files and I'm doing something with a 2nd TC instance in the foreground, the first instance claims that it has been aborted and stops.
This is of course especially annoying when the first instance is doing a search that takes a long time to finish, and this is also the primary reason why the 2nd instance is there at all.
Is this a known problem?
This is of course especially annoying when the first instance is doing a search that takes a long time to finish, and this is also the primary reason why the 2nd instance is there at all.
Is this a known problem?
[face=courier]On 07-06-2004 22:52:31 +0000 ghisler(Author) wrote:
g> Believe me, I really wrote a threaded version of search,
g> but it crashed all the time when searching in archives,
g> or worse, gave bad output without errors.
I do believe you, but:
1. Why don't you report about the problems you faced to unpack DLL's authors, e.g. about unrar.dll to Eugene Roshal?
2. Why don't you want to implement it for search only outside of archives?[/face]
g> Believe me, I really wrote a threaded version of search,
g> but it crashed all the time when searching in archives,
g> or worse, gave bad output without errors.
I do believe you, but:
1. Why don't you report about the problems you faced to unpack DLL's authors, e.g. about unrar.dll to Eugene Roshal?
2. Why don't you want to implement it for search only outside of archives?[/face]
[face=courier]The Protoss do NOT run from their enemies.
It is here, that we shall make our stand.[/face]
It is here, that we shall make our stand.[/face]