Updated version of ExifToolGui available on GitHub.

[FrankB]

An updated version of this great tool is available on GitHub: https://github.com/FrankBijnen/ExifToolGui/

It was intended to be a 'Source only' release, but I have also checked in the Executable. You can find it here.
For info on what has been updated, how to install, compile etc, read the info on GitHub.

The documentation is here.

Do I consider myself the maintainer of this program? No, but I will look into bugs found. It is also worth mentioning that the source code no longer relies on 3rd party libraries, so it is easier to maintain the code.

See also this post: https://exiftool.org/forum/index.php?topic=14981.0

PH edit: Updated link to download executable.
PH edit: Added documentation link.

[kevinf]

Great work Frank, you're amazing! Especially bypassing Google Maps to use OSM. I'm on Windows 10, only minor glitch was the degree symbol displaying as a diamond with a question mark inside.

[FrankB]

Thanks Kevin,

- About the Osm map: Work is in progress to add the search on city.
See: https://github.com/FrankBijnen/ExifToolGui/issues/3

- I'm still investigating an Access Violation that I sometimes get.

- Could you post a screenshot of the 'diamond with a question' and how to reproduce it?

Frank

[FrankB]

Ah you must mean these characters?
Will fix it. Give me some time. Watch this thread for updates

[kevinf]

Yes, those are the characters Frank. Thanks again.

[FrankB]

Created a new version: 6.0.3

This should fix the degree characters in the GPS coordinates. Also the searching on Cities has been re-enabled.

Frank

[obetz]

Thanks, Frank!

Just a suggestion: Program -> About should point to exiftool.org instead of queensu.ca and to your github repo.

And is it by intention that version 6.x writes "ExifToolGUIv5.ini"?

[FrankB]

Just a suggestion: Program -> About should point to exiftool.org instead of queensu.ca and to your github repo.

Good suggestion! I will create an issue in Github for them.

And is it by intention that version 6.x writes "ExifToolGUIv5.ini"?

No, not by intention. Will have a look to change that, with the option to transfer the settings from V5 to V6.

[kevinf]

Created a new version: 6.0.3

This should fix the degree characters in the GPS coordinates. Also the searching on Cities has been re-enabled.

Frank

Thanks once more!

[FrankB]

Just a suggestion: Program -> About should point to exiftool.org instead of queensu.ca and to your github repo.

And is it by intention that version 6.x writes "ExifToolGUIv5.ini"?

Created version 6.0.4 to fix the issues mentioned above.
Note: The new about has the option to open the links.

[FrankB]

And is it by intention that version 6.x writes "ExifToolGUIv5.ini"?

OK. A few days have past since I changed the INI filename, and I have been thinking about it. Wouldn't it be better to save the INI file in a directory that a 'normal user' can write to? (For example '%USERPROFILE%\documents\exiftoolgui')
Now the user gets an error saving the inif file, if the program is installed in 'Program Files (X86)'.

Also I would like to add a link to your exiftool installer 'https://oliverbetz.de/pages/Artikel/ExifTool-for-Windows' in the About Box. Are you OK with that?

Frank

[herb]

Hello Frank B,

thanks for updating ExifToolGUI to version 6.x

'%USERPROFILE%\documents\exiftoolgui'

This is a very good idea - BUT it should be C:\users\<user>\AppData\ExifToolGui.
And please read this value via the corresponding registry-key.

I also have another wish:
On my system I have installed >1 version of exiftool.
ExiftoolGui should use a setting to find where ExifTool is really installed.

Thanks in advance
Best regards
herb

[FrankB]

Hi Herb,

Thanks for your feedback. Really appreciate it, but I do have some questions.

This is a very good idea - BUT it should be C:\users\<user>\AppData\ExifToolGui.
And please read this value via the corresponding registry-key.

I see what you mean. An INI file is not a document. I was thinking of using the ShGetFolderPath API with the CSIDL_APPDATA constant. See  https://learn.microsoft.com/en-us/windows/win32/api/shlobj_core/nf-shlobj_core-shgetfolderpatha
Edit: Better to use shgetknownfolderpath: https://learn.microsoft.com/en-us/windows/win32/api/shlobj_core/nf-shlobj_core-shgetknownfolderpath with FOLDERID_RoamingAppData

That will get a directory in the 'Roaming' part, I hope that is what you mean! E.G.: C:\Users\username\AppData\Roaming\ExifToolGUI\

I also have another wish:
On my system I have installed >1 version of exiftool.
ExiftoolGui should use a setting to find where ExifTool is really installed.

Actually I dont see a problem with the way it works right now. It will find the Exiftool.exe in the Path, in my case that's good enough. I'm open to suggestions though. How should your proposed setting work? Can you explain briefly? Or point me to another application that works that way?

Frank

[herb]

Hello Frank B

It will find the Exiftool.exe in the Path

This is a very good solution in case of you have only 1 instance of ExifTool installed.
But with >1 ExifTool versions installed I see a problem, because you always have to modify the Path-variable.
In case you forget it, you do not know which version is used.

I think it will be much better to only modify an ExifToolGUI setting.

Best regards
herb

[obetz]

Also I would like to add a link to your exiftool installer 'https://oliverbetz.de/pages/Artikel/ExifTool-for-Windows' in the About Box. Are you OK with that?

No problem for me, but I wouldn't put this link hard coded in the "About" box. Maybe Readme.md in your HitHub repository or other ExifToolGui documentation is the better place. The download link to my package might change sooner or later.

Regarding the docs: Do you know https://exiftool.org/gui/ ? You should either link to it or even better incorporate it in your release (not sure about license/copyright).

Regarding binary releases: I suggest not to use "Source/Win32/Release" but the "releases" function of GitHub https://docs.github.com/repositories/releasing-projects-on-github/about-releases