Bilingual error message with quick view of locked file
Moderators: Hacker, petermad, Stefan2, white
Bilingual error message with quick view of locked file
When I try to quick view a TIF file (with ImgView) while the file is also open in the MS Office Document Imaging application then I get the bilingual error message: "Datei filename kann nicht geoffnet werden. The process cannot access the file because it is being used by another process". I suppose the error is correct but it should be all the same language. Not sure of this is TC7 or ImgView related.
One part of the message may come from the plugin while the other - from the system. There are some API calls that allow to get information about the cause of the error, but Windows returns the text in its "native" language, of course.
Flint's Homepage: Full TC Russification Package, VirtualDisk, NTFS Links, NoClose Replacer, and other stuff!
Using TC 11.03 / Win10 x64
Using TC 11.03 / Win10 x64
hoogenpi
Maybe, the plugin ImgView has German messages inside.
Maybe, the plugin ImgView has German messages inside.
Flint's Homepage: Full TC Russification Package, VirtualDisk, NTFS Links, NoClose Replacer, and other stuff!
Using TC 11.03 / Win10 x64
Using TC 11.03 / Win10 x64
Yes !
2Flint
Hello K. !
and not translatable normally since there is no LNG file…
FR
Claude
Clo

• Right ! I checked, and I can confirm that some error-messages are in German,Maybe, the plugin ImgView has German messages inside.
and not translatable normally since there is no LNG file…


Claude
Clo
#31505 Traducteur Français de T•C French translator Aide en Français Tutoriels Français English Tutorials
- ghisler(Author)
- Site Admin
- Posts: 50471
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Please write to him that a lister plugin should NEVER show any error! It should just return NULL as the window, so the next plugin (or lister itself) can access the file!
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
I don't fully understand why the lister plugin should never show any error. For example, the ImgView plugin doesn't support all compression schemes of the TIF file format. When unsupported compression is used the plugin generates an error message so the user knows what is going on. Without the message the user would have to guess.
If no errors are returned then the next plugin can access the file but when would that happen and what would be the purpose? Can more than one plugin be used to view a file with for example a TIF extension and if the first one fails the second one can try to display the file?
If no errors are returned then the next plugin can access the file but when would that happen and what would be the purpose? Can more than one plugin be used to view a file with for example a TIF extension and if the first one fails the second one can try to display the file?
Yep.Can more than one plugin be used to view a file with for example a TIF extension and if the first one fails the second one can try to display the file?

Roman
Mal angenommen, du drückst Strg+F, wählst die FTP-Verbindung (mit gespeichertem Passwort), klickst aber nicht auf Verbinden, sondern fällst tot um.
- ghisler(Author)
- Site Admin
- Posts: 50471
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Yes, that's EXACTLY the reason! For example, I always get an error from ImgView when switching through plugins by pressing the '4' key, and ImgView doesn't like the format - but all I wanted to achieve is to open the file with a plugin which comes after ImgView...Can more than one plugin be used to view a file with for example a TIF extension and if the first one fails the second one can try to display the file?
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
OK, that's clear. Michael made a new version of ImgView that makes showing the error messages optional (through a context menu setting) so that satisfies both our needs. The new version also allows files to be viewed which are in use. I found some other potential issues with the new version so I don't think it is ready for release yet.