TC calls ContentGetValue after abort
Moderators: Hacker, petermad, Stefan2, white
- ghisler(Author)
- Site Admin
- Posts: 50390
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
This doesn't make any sense to me - does it request them in the foreground thread, or the background thread?
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
- ghisler(Author)
- Site Admin
- Posts: 50390
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Sorry, I missed this - it explains the problems you have:Forgot to mention this in the first post. I'm using TC 8.01 64 bit on win7.
The problem was that you had multiple slow fields for one file (in a single line of the file list). In TC 8.01 and older, the icon extract queue treats each line as a separate item. Aborting one field in such a line still extracted the rest of the line. TC 8.5 now also discards the rest of the line if there are more fields behind the aborted one.
Please try with TC 8.5 beta, it should already be fixed there.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
Oh my gosh
!
---
p.s.: Sorry, but I have to say that this was clearly, and drastically, a failure of communication!
And there's more than one culprit involved.
So let's plz all keep it in mind as a bad example and try to avoid such a waste and unnecessary frustration in the future.
>>> Make (and maintain) as concise a description as possible, in ONE PLACE - and don't forget to prominently state which version/system combinations it has been reproduced on.
And, last but not least, read carefully.

Confirmed, in 8.5ß13 it doesn't happen anymore. Thanksghisler wrote:Please try with TC 8.5 beta, it should already be fixed there.

---
p.s.: Sorry, but I have to say that this was clearly, and drastically, a failure of communication!
And there's more than one culprit involved.
So let's plz all keep it in mind as a bad example and try to avoid such a waste and unnecessary frustration in the future.
>>> Make (and maintain) as concise a description as possible, in ONE PLACE - and don't forget to prominently state which version/system combinations it has been reproduced on.
And, last but not least, read carefully.