TC IrfanView Plugin

[tuska]

because that will certainly save a lot of forum inquiries over time.

OK

because I am not sure if I should add this not expected behavior with ContextMenu=1

It is better to add. Let Ghisler know about it. And then it's up to him how to react to it.

Thank you for your answer.
I have added the topic in the bug forum.

[AkulaBig]

Version 1.8.5:
* internal changes.

[ghisler(Author)]

To the plugin author:
The context menu problems are a bug in Total Commander 11 beta, please do not try to fix them!

[AkulaBig]

To the plugin author:
The context menu problems are a bug in Total Commander 11 beta, please do not try to fix them!

I see. Thanks for the information.

[tuska]

Version 1.8.5:
* internal changes.

Thank you for the new version!

Nothing has changed in the problem 2.a.

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.

in TC 11.00b7 x86 (started WITHOUT administrative rights).

I'm not sure if this will then be solved with the bug fix for the context menu as well.
But we will see...

[AkulaBig]

But we will see...

We have to wait until the release. There is no point in testing anything on beta. And in any case, this does not apply to the plugin in any way. I don't use any access rights.

[tuska]

We have to wait until the release. There is no point in testing anything on beta.

That is clear to me.
I was only interested in the new TC IrfanView Plugin version 1.8.5 - 18.6.2023.

... And in any case, this does not apply to the plugin in any way. I don't use any access rights.

Mmh, for me it is still unclear at the moment why I can use my own .ini
in TC IrfanView Plugin version 1.8.5 x64 version and not in the x86 version.

But let's wait for now.

[AkulaBig]

Mmh, for me it is still unclear at the moment why I can use my own .ini
in TC IrfanView Plugin version 1.8.5 x64 version and not in the x86 version.

But let's wait for now.

Do the file attributes match? Maybe for x86 read only?

[AkulaBig]

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.
And in TC 11 beta in x64, the context menu doesn't work for me either. The menu appears, but the items are not pressed.

[tuska]

Do the file attributes match? Maybe for x86 read only?

Yes, they match.
a Archive

Mmh, for me it is still unclear at the moment why I can use my own .ini

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.

I tested many things and finally found the solution for x86: See point 6.

1. c:\Program Files\totalcmd\Plugins\wlx\TCIrfanView\irfanview.ini [Options] - otherwise empty
2. c:\Program Files\totalcmd\Plugins\wlx\TCIrfanView\IrfanView\ - i_view32.ini is NOT taken into account by the plugin!
   The IrfanView installation files must be located in this folder!

   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--

3. C:\Users\user\AppData\Roaming\IrfanView\ - i_view32.ini is NOT taken into account by the plugin!

   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--

4. C:\Program Files (x86)\IrfanView\ - i_view32.ini is NOT taken into account by the plugin! -> See: Points 5. and 6.

   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--

5. %LOCALAPPDATA%\VirtualStore\Program Files (x86)\IrfanView\i_view32.ini this corresponds to:
   C:\Users\user\AppData\Local\VirtualStore\Program Files (x86)\IrfanView\ - i_view32.ini is NOT taken into account by the plugin!

   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--

   This i_view32.ini is changed when you call C:\Program Files (x86)\IrfanView\i_view32.exe and make a change, e.g. the language.
    
6. C:\Users\user\AppData\Local\VirtualStore\Program Files\totalcmd\Plugins\wlx\TCIrfanView\IrfanView\

   Code: Select all

   Name/Ext									Size	  Date			Attr
   --------------------------------------------------------------------------------------------------------------------
   i_view32.ini									29 116	  19.06.2023 01:14	-a--

   This i_view32.ini is used by the Lister (irfanview) x86:
   C:\Users\user\AppData\Local\VirtualStore\Program Files\totalcmd\Plugins\wlx\TCIrfanView\IrfanView\i_view32.ini
   I.e. if one closes e.g. the Lister window with ESC this file is updated!
   I.e. for changes one must call c:\Program Files\totalcmd\Plugins\wlx\TCIrfanView\IrfanView\i_view32.exe in this case,
   because these are stored in the i_view32.ini in the before mentioned path and considered with renewed call of the
   F3 Lister (irfanview). You can also edit the file "i_view32.ini" with a text editor
   and in the section [Viewing] change the value ContextMenu=0 to 1 (context menu available).
   
   After clicking into the image
   - F2 Rename is possible
   - the context menu can be opened with a right click
   - the image view can be zoomed in/out by pressing the "F" key several times

⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺
As another installation variant, this also works:
c:\Program Files\totalcmd\Plugins\wlx\TCIrfanView\irfanview.ini

Code: Select all

[Options]
path=C:\Users\user\AppData\Local\VirtualStore\Program Files\totalcmd\Plugins\wlx\TCIrfanView\IrfanView\i_view32.ini

The IrfanView - installation files must still be in this folder, because the i_view32.exe may be needed for changes
(these can be made much easier via the settings menu). The advantage with this variant is that I know where the settings file is located.
⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺
 
Question: - Meanwhile obsolete, since the answer is 6.
If the following is present:
0. c:\Program Files\totalcmd\Plugins\wlx\TCIrfanView\irfanview.ini [Options] - otherwise empty
1. C:\Program Files (x86)\IrfanView\i_view32.ini [Others] INI_Folder=%APPDATA%\IrfanView
2. C:\Users\user\AppData\Roaming\IrfanView\i_view32.ini
3. C:\Program Files (x86)\IrfanView\i_view32.ini
4. c:\Program Files\totalcmd\Plugins\wlx\TCIrfanView\IrfanView\i_view32.ini
5. C:\Users\user\AppData\Local\VirtualStore\Program Files (x86)\IrfanView\i_view32.ini
6. C:\Users\user\AppData\Local\VirtualStore\Program Files\totalcmd\Plugins\wlx\TCIrfanView\IrfanView\i_view32.ini
which i_view32.ini does your plugin access in this case?

And in TC 11 beta in x64, the context menu doesn't work for me either. The menu appears, but the items are not pressed.

Yes, this is exactly the bug that will be fixed in the next beta version (already confirmed by Mr. Ghisler).

PS:
Until now I do not know which i_view64.ini is used for the TC IrfanView plugin
in c:\Program Files\totalcmd\Plugins\wlx\TCIrfanView\IrfanView64\.

⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺
Windows 11 Pro (x64) Version 22H2 (OS Build Build 22621.1848)

[AkulaBig]

Until now I do not know which i_view64.ini is used for the TC IrfanView plugin

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.

[tuska]

You are completely confused.

Now only half as much, because I solved x86 c:\Program Files.
Only x64 in c:\Program Files is still open for me. ***)
Everything else (c:\totalcmd) is done.

Until now I do not know which i_view64.ini is used for the TC IrfanView plugin

Once again - my plugin does not set access to i_view32(64).ini.

Yes, I know that now too.
I was just wondering as a user what actually the c:\Program Files\totalcmd\Plugins\wlx\TCIrfanView\IrfanView\i_view32.ini does,
which comes with the plugin installation, and only now realized that it is not used by the plugin at all.

IrfanView ALWAYS accesses i_view32(64).ini in the folder where IrfanView is installed.

Yes, this statement unfortunately does not help with a TC IrfanView plugin installation.

***)
This is SOLVED:
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.
It is not enough to transfer the installation from e.g. C:\totalcmd\Tools\IrfanView-portable-64bit\IrfanView\
to c:\Program Files\totalcmd\Plugins\wlx\TCIrfanView\IrfanView64\!

This leaves only the context menu in TC IrfanView Plugin 1.8.5 x64 open for me.
From now on I'm just waiting for TC 11.00b8 on this topic.

[AkulaBig]

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.

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.

It is not enough to transfer the installation from e.g. C:\totalcmd\Tools\IrfanView-portable-64bit\IrfanView\
to c:\Program Files\totalcmd\Plugins\wlx\TCIrfanView\IrfanView64\!

The best location for me:
c:\PortablePrograms\FileManagers\TotalCommanderPortable\TOTALCMD.EXE
c:\PortablePrograms\FileManagers\TotalCommanderPortable\TOTALCMD64.EXE
c:\PortablePrograms\FileManagers\TotalCommanderPortable\Plugins\wlx\TCIrfanView\IrfanView\i_view32.exe
c:\PortablePrograms\FileManagers\TotalCommanderPortable\Plugins\wlx\TCIrfanView\IrfanView64\i_view64.exe
In this case, all files have access. And the programs can be carried on a USB stick. I assign Windows associations directly along these paths.

[Horst.Epp]

The IrfanView context menu problem in the x64 version of the plugin
is solved with beta8

[tuska]

To the plugin author:
The context menu problems are a bug in Total Commander 11 beta, please do not try to fix them!

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)

2ghisler(Author)
Thank you for the prompt bugfix in TC 11.00b8 x64
concerning the context menu of TC IrfanView Plugin 1.8.5 x64!

i_view64.ini

Code: Select all

[Viewing]
ContextMenu=1

---

Tested:
TC IrfanView Plugin 1.8.5 (x86), (x64) TC IrfanView Plugin 2.59 (x86), (x64) - F3 Lister (irfanview), Ctrl+Q, Ctrl+Q + Tab + 4,
Context menu (right click in the image), F2 Rename, F (zoom in/out), key 4 (plug-in change), ESC key.

Installation directories
- Total Commander (x64) 11.00b8 in C:\totalcmd (portable)
- Total Commander (x86) 11.00b8 in C:\totalcmd (portable)
- Total Commander (x64) 11.00b8 in C:\Program Files\totalcmd
- Total Commander (x86) 11.00b8 in C:\Program Files\totalcmd

Windows 11 Pro (x64) Version 22H2 (OS build Build 22621.1848) | TC 11.00b8 x64/x86

Notes about the TC IrfanView Plugin 1.8.5

1. If one calls after F3 Lister (irfanview) any functions of the Plugin, like e.g. context menu by right click,
   F2 Rename, F key (zoom in/out), then it is not possible to switch to another plugin with the key 4.
   In this case it is necessary to select another plugin via menu "Plugins", e.g. PhotoViewer.
   From then on the plugin change works again with key 4.
2. Ctrl+Q, tab, context menu by right click does not exist in this case (but only with F3 Lister (irfanview)).
   However, if one changes with key 4, e.g. to the PhotoViewer, then after Ctrl+Q in the opposite window
   the context menu of PhotoViewer is also available.