Thank you for your answer.
I have added the topic in the bug forum.
Moderators: white, Hacker, petermad, Stefan2
I see. Thanks for the information.ghisler(Author) wrote: ↑2023-06-18, 09:09 UTC To the plugin author:
The context menu problems are a bug in Total Commander 11 beta, please do not try to fix them!
Thank you for the new version!
in TC 11.00b7 x86 (started WITHOUT administrative rights).HISTORY.TXT wrote:c:\Program Files\totalcmd\Plugins\wlx\TCIrfanView\IrfanView\i_view32.ini
Unlike the x64 version, with the x86 version I can NOT select my own .ini file, i.e. it has no effect.
That is clear to me.
Mmh, for me it is still unclear at the moment why I can use my own .ini
I found time to experiment with protected folders and with TC 11 beta. In general, as I wrote earlier, the availability of their files depends on the bit depth of the TC and IV. You should have tried not the plugin itself, but the IV separately. Then you would have seen how access to the configuration files depends on the bit depth of the IV. And the best option, if you install IV in protected folders, is to place its ini in AppData. It's the same for TC. Then there will always be access to them. My plugin has nothing to do with this.
Yes, they match.
I tested many things and finally found the solution for x86: See point 6.AkulaBig wrote: ↑2023-06-18, 15:01 UTCIn general, as I wrote earlier, the availability of their files depends on the bit depth of the TC and IV.
You should have tried not the plugin itself, but the IV separately.
Then you would have seen how access to the configuration files depends on the bit depth of the IV.
And the best option, if you install IV in protected folders, is to place its ini in AppData.
It's the same for TC. Then there will always be access to them. My plugin has nothing to do with this.
Code: Select all
Name/Ext Size Date Attr
--------------------------------------------------------------------------------------------------------------------
i_view32.ini 340 18.06.2023 15:39 -a--
i_view32_AkulaBig.ini 7 106 18.06.2023 09:12 -a--
i_view32_C-Program Files (x86).ini 42 14.06.2023 11:29 -a--
i_view32_my own.ini 29 116 15.06.2023 19:59 -a--
i_view32_Original after installation.ini 242 14.06.2023 11:25 -a--
i_view32_Original after installation inclusive section [Registration].ini 340 18.06.2023 15:39 -a--
Code: Select all
Name/Ext Size Date Attr
--------------------------------------------------------------------------------------------------------------------
i_view32.ini 340 18.06.2023 15:39 -a--
i_view32_my own.ini 29 116 15.06.2023 19:59 -a--
i_view32_Original after installation.ini 242 14.06.2023 11:25 -a--
i_view32_Original after installation inclusive section [Registration].ini 340 18.06.2023 15:39 -a--
Code: Select all
Name/Ext Size Date Attr
--------------------------------------------------------------------------------------------------------------------
i_view32.ini 29 214 17.06.2023 11:10 -a--
i_view32_Original after installation.ini [Others] INI_Folder=%APPDATA%\IrfanView 42 14.06.2023 11:29 -a--
Code: Select all
Name/Ext Size Date Attr
--------------------------------------------------------------------------------------------------------------------
i_view32.ini 29 108 18.06.2023 19:59 -a--
i_view32_current .ini file_of C-Program Files (x86)-IrfanView.ini 1 664 18.06.2023 19:40 -a--
i_view32_my own.ini 29 116 15.06.2023 19:59 -a--
Code: Select all
Name/Ext Size Date Attr
--------------------------------------------------------------------------------------------------------------------
i_view32.ini 29 116 19.06.2023 01:14 -a--
Code: Select all
[Options]
path=C:\Users\user\AppData\Local\VirtualStore\Program Files\totalcmd\Plugins\wlx\TCIrfanView\IrfanView\i_view32.ini
Yes, this is exactly the bug that will be fixed in the next beta version (already confirmed by Mr. Ghisler).
You are completely confused. You need to understand that access to files in protected folders is controlled by Windows, not my plugin. You need to check the work of the IV itself. And not my plugin to understand how access to i_view32(64).ini happens. Once again - my plugin does not set access to i_view32(64).ini. My plugin DOES NOT READ i_view32(64) at all.ini. IrfanView ALWAYS accesses i_view32(64).ini in the folder where IrfanView is installed. And if [Others] INI_Folder=%APPDATA%\IrfanView is written in i_view32(64).ini, then IrfanView, and NOT MY PLUGIN, refer to %APPDATA%\IrfanView\i_view32(64).ini.
Now only half as much, because I solved x86 c:\Program Files.
Yes, I know that now too.
Yes, this statement unfortunately does not help with a TC IrfanView plugin installation.
I am very glad that you have finally understood this. If you install the program in protected folders, it is necessary that its configuration files are stored in folders that you have access to.tuska wrote: ↑2023-06-19, 01:56 UTC The IrfanView x64 - installation must be done in this folder: c:\Program Files\totalcmd\Plugins\wlx\TCIrfanView\
and this menu item must be selected: ◉ "Application data" directory recommended.
This results in: C:\Users\user\AppData\Roaming\IrfanView\i_view64.ini.
The best location for me:
ghisler(Author) wrote: ↑2023-06-18, 09:09 UTC To the plugin author:
The context menu problems are a bug in Total Commander 11 beta, please do not try to fix them!
2ghisler(Author)HISTORY.TXT wrote:21.06.23 Release Total Commander 11.00 beta 8
16.06.23 Fixed: Lister: Several problems with right click context menu resolved,
like shown twice after one right click, interference with plugins (32/64)
Code: Select all
[Viewing]
ContextMenu=1