rg_software wrote: 2025-05-22, 00:52 UTC
Yeah, "fit-to-screen" would be better
Yes. This is logical.
rg_software wrote: 2025-05-22, 00:52 UTC
Edge has built-in support for MHT, which the embedded Chromium engine lacks, unfortunately.
I checked on other chromium -like browsers. This file opens correctly. Take your time. If not now, then in the future it may be possible to resolve the issue.
rg_software wrote: 2025-05-22, 00:52 UTC
Another question: when you press 'F' to fit-to-screen, will this mode survive across files (F3/<ESC>/F3 and Quick view/File navigation)? If not, should it?
"F" works only for the current file in both viewing modes. I think this is correct. The main mode is set in the Ini file. It works for all files in any viewing mode.
AkulaBig wrote: 2025-05-22, 01:42 UTC
I checked on other chromium -like browsers. This file opens correctly. Take your time. If not now, then in the future it may be possible to resolve the issue.
If you are interested in technical details, Standalone Chromium-based browsers have this feature flag (--save-page-as-mhtml) deprecated but still supported. In embedded WebView2, this functionality is completely unavailable.
rg_software wrote: 2025-05-22, 02:23 UTC
MHTML update:
Try this file instead of the current mhtml2html.min.js inside assets/html.
Yes. My file shows normally! And there are no deus-ex files.
rg_software wrote: 2025-05-22, 02:27 UTC
If you are interested in technical details, Standalone Chromium-based browsers have this feature flag (--save-page-as-mhtml) deprecated but still supported. In embedded WebView2, this functionality is completely unavailable.
OK. Understood.
rg_software wrote: 2025-05-22, 03:54 UTC
Also, this loader inside imgview should work with any keyboard layout, regardless of the currently set language.
rg_software wrote: 2025-05-22, 00:52 UTC
Another question: when you press 'F' to fit-to-screen, will this mode survive across files (F3/<ESC>/F3 and Quick view/File navigation)? If not, should it?
I think it should, because I understand it as a toggle. For example, with the image viewer plugin Imagine, you can quick-view images and switch fit-to-screen on/off anytime, the current setting is remembered (saved to INI-file) and transitioned to the next viewed image.
Perhaps add a flag to the INI file, indicating whether the state of fit-to-screen should be persistent, so everyone can choose their flavor.
deus-ex wrote: 2025-05-22, 07:32 UTC
Perhaps add a flag to the INI file, indicating whether the state of fit-to-screen should be persistent, so everyone can choose their flavor.
There is already such a flag:
[Images]
FullScreen=0
Therefore, I agreed that the state "F" should not be remembered.
AkulaBig wrote: 2025-05-22, 10:03 UTC
There is already such a flag:
[Images]
FullScreen=0
Therefore, I agreed that the state "F" should not be remembered.
This flag controls the view state at the plugin start-up. Therefore, it also resets the view to the predefined state in quick-view mode when advancing to the next image, which I find rather distracting.
Therefore, my suggestion is to make it a persistent toggle. To compensate for users who don't want that functionality, add another flag that allows control over whether the fit-to-screen toggle should remember the last user input.
The fit-to-screen flag could be designed to accept different values: 0 = always off, 1 = always on, 2 = remember last user input
AkulaBig wrote: 2025-05-22, 07:07 UTC
And there are no deus-ex files.
I'm sorry, what did you try to say?
I just checked my uploaded example MHTs with the updated mhtml2html.min.js. For me, there is no change on the reported issues.
deus-ex wrote: 2025-05-22, 13:18 UTC
I just checked my uploaded example MHTs with the updated mhtml2html.min.js. For me, there is no change on the reported issues.
This is what I wrote. Watching your files does not work.
