Version V6.1.0 available on Github! (August 19, 2023)

[FrankB]

This is only meant to draw your attention to version:
https://github.com/FrankBijnen/ExifToolGui/releases/tag/V6.1.0

[herb]

Hello FrankB,

thanks for the new versions of ExifToolGUI and also thanks that it is possible to specify the path to ExifTool.

But I have 2 questions:
(1) In order to see the changes to version 6.1.0 I have both versions installed and I have seen that I now have 2 *.ini files in 2 different directories.
Sorry to say, but I do not see any advantage with this solution.
I would like to propose: only 1 *.ini file for all versions in only one directory. Both should not have a "version-string"n in its name.

(2) With version 6.1.0 I have seen in workspace non-printable characters.
E.g. for typexx which looks in version 6.0.5: type+-
Do I need a special font or is it a fault in ExifToolGUI?

Best regards
herb

[FrankB]

Hello Herb,

Appreciate your feedback.

1) Location and name of the ini file. The way it works now that the program will ALWAYS write to ExifToolGUIV6.ini in the <Userdir>\AppData\Roaming\ExifToolGUI directory. (for Win32)
At program start, if the program does not find the ini file there, it READS the settings from ExifToolGuiV5.ini in the program directory. That way it tries to migrate your settings.

It can very well be the case that you have multiple INI files now, because the program does not try to delete the old INI files.
This was discussed in: https://exiftool.org/forum/index.php?topic=15053.6

Right now I dont see what needs to be changed.

2) PLusMinus signs
These settings are also stored in the INI file. The INI file is stored, as in V5, in ANSI format.

If I delete all ExifToolGUIV6.ini files and start the program it recreates the INI file. On my system it looks OK. See the screenshot.

Could you try?

- Rename your INI file.
- Start the program.
- If it displays the plusminus signs correct, I would like the renamed INI file.
- If it is still incorrect, I would like the new INI file.

- Or compare it yourself

Frank

[herb]

Hello FrankB,

thanks for your quick reply.

ad (1)

will ALWAYS write to ExifToolGUIV6.ini in the <Userdir>\AppData\Roaming\ExifToolGUI directory

Sorry, but I cannot agree.
For *.exe file - <base>.exe - it writes file <base>V6.ini in directory <Userdir>\AppData\Roaming\<base>
e.g.: ExifToolGUI_X64_V6.1.0V6.ini in directory ExifToolGUI_X64_V6.1.0
Here I see a problem in case of >1 ExiftoolGui.exe installed (especially in one directory).
I again propose to really use only: ExifToolGUIV6.ini in directory ...\ExifToolGUI

ad (2)
I followed you proposal 2 times before I posted the problem.
No I downloaded the *.exe again and started from scratch. To my surprise I cannot reproduce the error.
Sorry.

Best regards
herb

[FrankB]

Hello Herb,

Thanks for replying immediately. I like that!

1) Ah. Now I understand you!
You dont mind the V5, V6 suffix, but the 'base name'.

First let me explain why that occurs. The program takes the name of the executable and uses that for its 'base name'.
The fact is that 'Bogdan's version V5' already did that, and I did not change that. You can verify that by renaming the V5 executable to lets say 'ExifToolGui_blabla.exe' and check what ini file it creates. This has now become apparent because I renamed the X64 executable to ExifToolGui_X64.exe in the release. If you build the program from source the name stays the same and it is not noticed.

If I understand you correctly you always want to have ExifToolGuiVn.ini no matter how the executable is named. I'll create an issue for that in Github.

As a workaround you could save the X64 executable in a different folder and name it ExifToolGui.exe. (That is how it works in my build environment)

See Maindefs.pas line 118

2) Thanks. Please dont hesitate to contact me if occurs again. I would like to get all Bugs resolved.

Frank