Updated version of ExifToolGui available on GitHub.

Started by FrankB, July 28, 2023, 05:03:45 PM

Previous topic - Next topic

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

Quote from: obetz on August 01, 2023, 02:37:18 AMJust 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.

Quote from: obetz on August 01, 2023, 02:37:18 AMAnd 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

Quote from: FrankB on July 31, 2023, 04:55:27 PMCreated 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

Quote from: obetz on August 01, 2023, 02:37:18 AMJust a suggestion: Program -> About should point to exiftool.org instead of queensu.ca and to your github repo.
Quote from: obetz on August 01, 2023, 02:37:18 AMAnd 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.
newabout.jpg

FrankB

Quote from: obetz on August 01, 2023, 02:37:18 AMAnd 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

Quote'%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

#12
Hi Herb,

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

Quote from: herb on August 06, 2023, 12:25:21 PMThis 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\

Quote from: herb on August 06, 2023, 12:25:21 PMI 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

QuoteIt 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

Quote from: FrankB on August 06, 2023, 08:28:04 AMAlso 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

obetz

Quote from: herb on August 06, 2023, 04:02:52 PMI think it will be much better to only modify an ExifToolGUI setting

I agree. If nothing is set in ExifToolGUI*.ini, first look in the ExifToolGui directory, then in the path.

FrankB

@obetz

All good advice. Thanks.

Give me some time to think about, I will get back on it.

FrankB

Quote from: herb on August 06, 2023, 04:02:52 PMI think it will be much better to only modify an ExifToolGUI setting.

Hello Herb.
Just released V6.0.5, that adds the option to specify the exiftool.exe location in Preferences/other.

Please let me know what you think of it.
Frank

FrankB

Quote from: obetz on August 07, 2023, 04:19:05 AMNo 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

Hello Oliver,

Just released V6.0.5, it addresses the issues mentioned above.
Please contact me, if I have misunderstood something. Thanks again for your feedback.

Frank

FrankB

Release V6.0.5 available on Github. https://github.com/FrankBijnen/ExifToolGui

FrankB

Version V6.1.0 released: https://github.com/FrankBijnen/ExifToolGui/releases/tag/V6.1.0

Please note that I dont intend to be adding new features for a while. (Dont have ideas!)
But I'm open to suggestions, and will look at Bugs.

Frank

FrankB

Version V6.1.1 released: https://github.com/FrankBijnen/ExifToolGui/releases/tag/V6.1.1

Some fixes, most noticeable the contextmenus, and shortcuts Ctrl/C, Ctrl/X and Ctrl/V added to the ShellList.
See the changelog.

Frank

lajip

Hi there. Awesome news that ExifTool GUI is reloaded!
I've encountered a bug in v5, I don't know yet if it's been fixed in v6. In a workspace, when there's two entries with the same tag name from different namespaces, there's an error message « list index out of bounds Â». I'll try v6 very soon, but wanted to have some pre-info on that issue in the meantime  :)

Thanks for your hard work!

FrankB

Thanks!

If haven't looked at that specific case. I did introduce a check that the nr. of results should be equal to the nr. of commands. Dont know if that fixes your case.

BTW I'm working very hard on a new release V6.2 with improved UTF8 support and an enhanced log Window. Expect to release it in a few weeks.

lajip

#24
Great, I'll check it out asap and report back any issue.
Edit: unfortunately the issue remains. I do get a popup window showing "Only X results returned. Your workspace has Y commands.", but then everything from V5 remains, i.e. some tags are missing in the Workspace, and the one that are showing up are mixed. As a test, you can for example add this to the ini file:
PDF=-GUI-SEP
CreateDate=-PDF:CreateDate
XMP Create Date=-XMP-xmp:CreateDate
XMP Toolkit=-XMP-x:XMPToolkit
-

On the feature side, I've always wondered why we can't add a tag to the workspace from the "ALL" view. It would be awesome to do so!
My use cases are mainly with PDF files, and the tags of the "PDF" namespace are only displayed in the "ALL" view; hence this request.

Also, being able to select multiple tags (with the usual CTRL and SHIFT modifier keys) and add them altogether to the Workspace, would be a time saver! It would be great to be able to do so.

Keep up the good work (y)

FrankB

Will look into it when I'm home. Next week or so.

I do have 1 question. How do you have the options setup? Especially 'Dont show duplicated tags'

Frank

FrankB

Look at the Changelog for Exiftool 12.66. https://exiftool.org/history.html
That should fix your problem.

I will look at the remarks, but that will be for a next release. I will create an issue in Github for those.

Frank


lajip

Sorry Franck for the delay. I have all my options set to default.
Thank you for considering my requests! Really appreciated.

If you need me to test something, please feel free to ask.

FrankB

If I have something to test I will gladly ask you to test.

But most important: Does upgrade to Exiftool 12.66, or 12.67 solve your problem? For me it works...
(Although I think ExiftoolGui could be better)

FrankB

Quote from: lajip on September 18, 2023, 05:33:31 PMOn the feature side, I've always wondered why we can't add a tag to the workspace from the "ALL" view. It would be awesome to do so!

Did a quick test, by enabling the button. Cant see whats wrong, so I'll enable it in the next release.

Quote from: lajip on September 18, 2023, 05:33:31 PMAlso, being able to select multiple tags (with the usual CTRL and SHIFT modifier keys) and add them altogether to the Workspace, would be a time saver! It would be great to be able to do so.

The control used "TValueListEditor" does NOT support Multi-select, so that's hard to implement. It would require extending the control. I think that's overkill.

What I CAN do is use Double Click for adding/removing Tags to the Workspace. I think that would already save you a lot of time. I would like to add a Checkbox in the Preferences/Other tab 'Double Click adds/removes tags to/from Workspace'. Are you happy with that?

lajip

Quote from: FrankB on September 23, 2023, 12:49:50 AMIf I have something to test I will gladly ask you to test.

But most important: Does upgrade to Exiftool 12.66, or 12.67 solve your problem? For me it works...
(Although I think ExiftoolGui could be better)
I'd have to double check with those versions; but it seems to related to the GUI, no?
You don't have the issue maybe because your sample PDF files don't have any PDF metadata in them.
I'll double check and will let you know.

Quote from: FrankB on September 24, 2023, 05:21:18 AM
Quote from: lajip on September 18, 2023, 05:33:31 PMOn the feature side, I've always wondered why we can't add a tag to the workspace from the "ALL" view. It would be awesome to do so!

Did a quick test, by enabling the button. Cant see whats wrong, so I'll enable it in the next release.

Quote from: lajip on September 18, 2023, 05:33:31 PMAlso, being able to select multiple tags (with the usual CTRL and SHIFT modifier keys) and add them altogether to the Workspace, would be a time saver! It would be great to be able to do so.

The control used "TValueListEditor" does NOT support Multi-select, so that's hard to implement. It would require extending the control. I think that's overkill.

What I CAN do is use Double Click for adding/removing Tags to the Workspace. I think that would already save you a lot of time. I would like to add a Checkbox in the Preferences/Other tab 'Double Click adds/removes tags to/from Workspace'. Are you happy with that?


Awesome for the first point. As far as for the second point, since it is too much work for multi-selection, I'd be more than happy with a double click (way faster then right click+mouse move+click).

Thanks Franck 🙏

FrankB

Quote from: lajip on September 24, 2023, 03:18:17 PMbut it seems to related to the GUI, no?

It IS an error in Exiftool 12.65 and fixed in 12.66. But I must admit that I have improved the handling of the error in GUI. No more MessageBoxes, but a warning in the MetaData grid.

If you send me your EmailAddress in a PM (Dont disclose it publicly) I will send you an updated version. Think of it as a pre-rel V6.2. That version has better support for international characters (Unicode/UTF8) and an enhanced Log Window. It shows the commands executed, plus the option to save them as a PowerShell, or Command script.

I'm curious to hear your opinion!
Frank

lajip

Frank, I tried ExifTool v12.67 and indeed it seems to be working fine now. Thanks for the heads-up, I feel better now :)

Sent you a PM ;)

FrankB

Version V6.2.5 available for download:
https://github.com/FrankBijnen/ExifToolGui/releases/tag/V6.2.5

More info:
https://github.com/FrankBijnen/ExifToolGui


rgiw

Ups ... just found it :)

---
Hi,
I cannot find the Windows executable under 'https://github.com/FrankBijnen/ExifToolGui/Source/Win32/Release'.
Did you move it?

Thanks
R

Phil Harvey

I see it when I click on the first link in Frank's last post.

Ah.  I see that the initial post in this thread gives the old location you were using.  I'll update this.

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

ChasaImago

Quote from: FrankB on July 28, 2023, 05:03:45 PMAn updated version of this great tool is available on GitHub: https://github.com/FrankBijnen/ExifToolGui/

Great!
After so many years; finally a new GUI. Thanks for that.

I use(d) the old ExifToolGUI almost every day to modify the images I shot and process with Photoshop.
Some of my work: https://flic.kr/s/aHsjDRXSan

But nevermind  8) , back to the fresh GUI.

I think I've came across a small, but for me, annoying bug:
When I resize the ExifToolGUI window and close it again, then when restarted, the original window size is not saved and the ExifToolGUI window size is still the previous (original?) size.
Other options DO seem to be saved correctly in the \AppData\Roaming\ExifToolGui\ExifToolGuiV6.ini file.

Any ideas what might go wrong here?

BTW: I'm using a Win10 system with dual 4K monitors connected to a NVIDIA Quadro P4000 graphics card.
All WinOS and video drivers are up-to-date.

[ExifToolGUI]
StartMax=0
WinTop=37
WinLeft=274
WinWidth=2695
WinHeight=1409
BrowseWidth=476
PreviewHeight=220
MetadataWidth=1054
MetadataTagWidth=144
DefaultDir=D:\IMAGES\
LogWinTop=106
LogWinLeft=108
LogWinWidth=580
LogWinHeight=1500
StdColWidth0=272
StdColWidth1=106
StdColWidth2=190
StdColWidth3=176
Def1ColWidth0=64
Def1ColWidth1=64
Def1ColWidth2=48
Def1ColWidth3=73
Def1ColWidth4=73
Def1ColWidth5=56
Def1ColWidth6=88
Def1ColWidth7=80
Def2ColWidth0=120
Def2ColWidth1=48
Def2ColWidth2=80
Def2ColWidth3=80
Def2ColWidth4=120
Def2ColWidth5=120
Def3ColWidth0=120
Def3ColWidth1=48
Def3ColWidth2=120
Def3ColWidth3=120
Def3ColWidth4=120


I've played around with some of the above values; but not one of them seems to make sure the window size is restored to its last-exit size...

www.panomeister.com

FrankB

Quote from: ChasaImago on December 09, 2023, 09:57:18 AMAfter so many years; finally a new GUI. Thanks for that.
You're welcome.

Quote from: ChasaImago on December 09, 2023, 09:57:18 AMSome of my work: https://flic.kr/s/aHsjDRXSan
Nice pics. Besides Exiftool(gui) & Photos I also like to ride a motorbike. Seems like a nice area for biking.

Quote from: ChasaImago on December 09, 2023, 09:57:18 AMBut nevermind  8) , back to the fresh GUI.

I think I've came across a small, but for me, annoying bug:
When I resize the ExifToolGUI window and close it again, then when restarted, the original window size is not saved and the ExifToolGUI window size is still the previous (original?) size.
Other options DO seem to be saved correctly in the \AppData\Roaming\ExifToolGui\ExifToolGuiV6.ini file.

Any ideas what might go wrong here?
- Gui should restore the window position.
- I assume you're using the latest version? V6.2.6.
- I can reproduce the behaviour if the shortcut to ExifToolGui is set to Maximized. PLease check your setting.

shortcut.jpg

ChasaImago

#38
Quote from: FrankB on December 09, 2023, 11:03:04 AM- Gui should restore the window position.
- I assume you're using the latest version? V6.2.6.
Yep.
Quote- I can reproduce the behaviour if the shortcut to ExifToolGui is set to Maximized. PLease check your setting.

shortcut.jpg
The setting is: 'Normal window'; but then it is NOT restored to its previous window size.
When I try 'Minimised'; it's of course just a icon on the task bar and a very small window when you switch to its active window with [Alt]+[Tab]
When I try 'Maximized', it's indeed taking up the whole screen.

So it's still not restoring to its previous window size @ exit.  :-\
Any other suggestions?

Thnkx.

[update]
found it!

I had to change the 'override high DPI scaling behaviour'
Clipboard_12-09-2023_01.jpg

www.panomeister.com

FrankB


FrankB

Good that you found it.

I'm unsure if I need to fix something in GUI. And certainly wouldn't know what.

Any suggestions?

FrankB

Version V6.2.7 available for download:
https://github.com/FrankBijnen/ExifToolGui/releases/tag/V6.2.7

More info:
https://github.com/FrankBijnen/ExifToolGui

ChasaImago

Hi Frank,

I've just tested your 6.2.7 version (with the latest ExifTool 12.71).
Running on Windows 10 Pro 10.0.19045. With 2 x 27" 4K IPS monitors. (160% scaling)

It seems that the resizing/restoring of the ExifToolGUI window is now retained properly with this setting:

Clipboard_12-28-2023_01.jpg

This is the difference between the two settings (with/without)
Clipboard_12-28-2023_02.jpg

It seems that only the text from the progam options is sized properly. The text in the indivual subwindows is not scaled differently
I've not found (yet) any other setting that might alter that behaviour.
www.panomeister.com

FrankB

Thanks for your testing efforts. That is what I need!

I have other reports that the scaling from the 'top file menu' behaves different from the other texts. I will look into it.

Glad you confirm the window positioning has now been fixed.

With version 6.2.7 the default is set to 'System aware', that's why you dont see a lot of differences. Except for the already mentioned file menu.

It should not be needed anymore to change the shortcut setting. This doc explains it in more detail.

https://github.com/FrankBijnen/ExifToolGui/blob/main/Docs/Readme%204K%20monitor.txt

Thanks again
Frank

brizzo

Thank you very much. I can't believe we have a gui update after so long. It's a wonderful job and it's working perfectly.

I have a question. In the original version there was a countdown timer when I applied the same change to multiple files. Is there a way to enable this feature? I found it very useful for knowing the progress of changes to hundreds of files, for example. Now I can't see the progress.

Version 5.16 image attached.


FrankB

You're welcome

The counter is still there, but has been moved to the statusbar, because I thought it would be cleaner. And I needed room for the execution mode (StayOpen/Classic)_

progress.jpg

Frank


brizzo

Thank you for the quick response.

I selected 30 files and applied changes, but the counter doesn't appear. Should I select some minimum quantity for the counter to appear?

Another thing I noticed is that the status bar doesn't appear when the window is maximized.

I still use Windows 7. Could it be something related?

FrankB

Quote from: brizzo on January 27, 2024, 03:29:29 PMI selected 30 files and applied changes, but the counter doesn't appear. Should I select some minimum quantity for the counter to appear?

No, there is no minimum required. As it works now, the counter only appears if used with th -r option.
I checked the 'old 516 version' and that does show the counter in the situation you describe. I will try to fix this for the next release.

Quote from: brizzo on January 27, 2024, 03:29:29 PMAnother thing I noticed is that the status bar doesn't appear when the window is maximized.

I still use Windows 7. Could it be something related?
Strange. Never saw this. Windows 7 should not be a problem for this.

This is how it looks in my Windows 7
taskbar W7.jpg

FrankB

Version V6.2.9 available for download:
https://github.com/FrankBijnen/ExifToolGui/releases/tag/V6.2.9

More info:
https://github.com/FrankBijnen/ExifToolGui

FrankB

Quote from: brizzo on January 27, 2024, 03:29:29 PMI selected 30 files and applied changes, but the counter doesn't appear. Should I select some minimum quantity for the counter to appear?

Just released 6.2.9, that should fix it.


brizzo


dgsjsj

FrankB, good afternoon. Please tell me in version 6.2.9, is it possible to highlight information about the lens or other parameters in color? So that when switching between pictures you can easily find them.

FrankB

Hello dgsjsj,

If I understand you correctly it is possible.
- In the Metadata panel switch to Exif, XMP, IPTC, Maker or ALL.
- Find the line you wish to mark. (You can use the Find edit box)
- Right click on that line.
- Click on Mark/Unmark Tag.

The Tag will be colored red. See also the online docs. Metadata panel

But I would like to suggest another method. Add the field(s) to the User defined fields.
- Set the Filelist to User Defined.
- Set the Metadata panel to Exif, Xmp or IPTC
- Find the line
- Right Click on that line
- Click on Add to Filelist details.

The column will be on the filelist, and you can see the field for all files at once. Sorting is possible by clicking on the Columnheading.

See also the online docs: FileList panel

mark.jpg


dgsjsj

Thank you for your quick response and detailed explanations. I found out why the Mark/Unmark Tag item was missing from the selection menu.
The fact is that I chose Russian in the settings. When selecting Exif Tool, the Mark/Unmark Tag standard works and turns red. Thank you for the work done on the graphical shell. I will gradually study docs: FileList panel. Good health and all the best. Best regards, Sergei.

FrankB

Thanks for posting back.

The fact that marking tags is not possible when you have set a language other then English I consider a bug.
I have created an issue in Github: to correct that.

Will be available in a next release.

milchtaich

#55
Thank you Frank for your great work.
One question, though. With the old version, I can move or copy files to or from directories using dragging and dropping in the application window. With the new version, this is no longer possible (on my Windows 10 machine). Files do not respond to the same mouse gestures. Is there any setting that needs to be changed to enable copying and moving?

FrankB

Hello milchtaich,

No sadly there is no setting to activate that. The old (V516) used commercial controls for the File and folder lists. These controls had that built-in. Since I'm using only free, open source, controls this is no longer available.

But there is a workaround for this, that I think works better. The problem with dragging and dropping is that it can occur when you did not expect it. (The mouse gets stuck sometimes)

How I would do it:

- Select, in the filelist the files, or even folders, you want to copy/move.
- Right click, and choose Copy or Cut.
- Select in the folder list the folder you want to copy/move to and Right Click.
- Choose Paste.

(Cut, Copy and Paste depending on your Windows language of course)

Hope you can live with this, because it would be pain to code this functionality myself

Frank

copy.jpg
paste.jpg


FrankB

Version V6.3.0 Released: https://github.com/FrankBijnen/ExifToolGui/releases/tag/V6.3.0

New features:
- Support for the new Exiftool features '-api geolocation' and '-geolocate'.
- Installer available, portable versions are still available.
- Translations available for Dutch, German, French, Italian, Spanish and Portuguese. They need to be checked, volunteers wanted!

Check out the changelog and other docs for more info.

Frank

FrankB


dgsjsj

The first time you open the V6.3.1 {ExifToolGui _X64.exe} program, an error occurs.

{ExifToolGui_X64.exe} ************************************* Access violation at address 0000000000E95B68 in module 'ExifToolGui_X64.exe'. Read of address 0000000000000000 *************************************
(0000000000314B68){ExifToolGui_X64.exe} [0000000000E95B68] Vcl.Themes.TCustomStyleServices.GetStyleFontColor + $8
(00000000003D7008){ExifToolGui_X64.exe} [0000000000F58008] JclDebug.JclCreateStackList + $48
(00000000003D6F16){ExifToolGui_X64.exe} [0000000000F57F16] JclDebug.DoExceptionStackTrace + $76
(00000000003D94F3){ExifToolGui_X64.exe} [0000000000F5A4F3] JclDebug.DoExceptNotify + $83
(00000000003CA085){ExifToolGui_X64.exe} [0000000000F4B085] JclHookExcept.TNotifierItem.DoNotify + $35
(00000000003CA2CB){ExifToolGui_X64.exe} [0000000000F4B2CB] JclHookExcept.DoExceptNotify + $BB
(00000000003CA487){ExifToolGui_X64.exe} [0000000000F4B487] JclHookExcept.HookedExceptObjProc + $37
(000000000000FDB7){ExifToolGui_X64.exe} [0000000000B90DB7] System.@DelphiExceptionHandler + $267
(00000000000A13AF){ntdll.dll   } [00007FFFA17B23AF] Unknown function at __chkstk + $11F
(00000000000504B4){ntdll.dll   } [00007FFFA17614B4] RtlRaiseException + $484
(000000000009FEBE){ntdll.dll   } [00007FFFA17B0EBE] KiUserExceptionDispatcher + $2E
(0000000000314B68){ExifToolGui_X64.exe} [0000000000E95B68] Vcl.Themes.TCustomStyleServices.GetStyleFontColor + $8
(00000000009B65F4){ExifToolGui_X64.exe} [00000000015375F4] ExifToolsGUI_Utils.StyledDrawListviewItem + $34
(0000000000993F6C){ExifToolGui_X64.exe} [0000000001514F6C] Main.TFMain.ShellListCustomDrawItem + $1C
(00000000002ADDB7){ExifToolGui_X64.exe} [0000000000E2EDB7] Vcl.ComCtrls.TCustomListView.CustomDrawItem + $57
(00000000002A9BC3){ExifToolGui_X64.exe} [0000000000E2ABC3] Vcl.ComCtrls.TCustomListView.CNNotify + $863
(000000000000E944){ExifToolGui_X64.exe} [0000000000B8F944] System.TObject.Dispatch + $44
(0000000000211F50){ExifToolGui_X64.exe} [0000000000D92F50] Vcl.Controls.TControl.WndProc + $360
(0000000000219407){ExifToolGui_X64.exe} [0000000000D9A407] Vcl.Controls.TWinControl.WndProc + $967
(00000000002AB931){ExifToolGui_X64.exe} [0000000000E2C931] Vcl.ComCtrls.TCustomListView.WndProc + $E1
(0000000000414521){ExifToolGui_X64.exe} [0000000000F95521] Vcl.Shell.ShellCtrls.TCustomShellListView.WndProc + $61
(0000000000836DF4){ExifToolGui_X64.exe} [00000000013B7DF4] ExifToolsGui_ShellList.TShellListView.WndProc + $64
(0000000000211A52){ExifToolGui_X64.exe} [0000000000D92A52] Vcl.Controls.TControl.Perform + $32
(00000000002195EE){ExifToolGui_X64.exe} [0000000000D9A5EE] Vcl.Controls.DoControlMsg + $2E
(000000000021A7DB){ExifToolGui_X64.exe} [0000000000D9B7DB] Vcl.Controls.TWinControl.WMNotify + $1B
(000000000000E944){ExifToolGui_X64.exe} [0000000000B8F944] System.TObject.Dispatch + $44
(0000000000211F50){ExifToolGui_X64.exe} [0000000000D92F50] Vcl.Controls.TControl.WndProc + $360
(0000000000219407){ExifToolGui_X64.exe} [0000000000D9A407] Vcl.Controls.TWinControl.WndProc + $967
(000000000021853C){ExifToolGui_X64.exe} [0000000000D9953C] Vcl.Controls.TWinControl.MainWndProc + $2C
(000000000013F096){ExifToolGui_X64.exe} [0000000000CC0096] System.Classes.StdWndProc + $26
(000000000000DF75){USER32.dll  } [00007FFF9FAAEF75] Unknown function at CallWindowProcW + $615
(000000000000D8DC){USER32.dll  } [00007FFF9FAAE8DC] Unknown function at DispatchMessageW + $6EC
(00000000000206D3){USER32.dll  } [00007FFF9FAC16D3] Unknown function at SendMessageTimeoutW + $143
(000000000009FE64){ntdll.dll   } [00007FFFA17B0E64] KiUserCallbackDispatcher + $24
(0000000000000124){win32u.dll  } [00007FFF9F4B1124] NtUserMessageCall + $14
(000000000000D0E3){USER32.dll  } [00007FFF9FAAE0E3] Unknown function at SendMessageW + $A53
(000000000000C81D){USER32.dll  } [00007FFF9FAAD81D] SendMessageW + $18D
(00000000000721CD){COMCTL32.dll} [00007FFF964431CD] Unknown function at CCSetScrollInfo + $F9D
(00000000000B1D89){COMCTL32.dll} [00007FFF96482D89] Unknown function at  + $19299
(000000000006D222){COMCTL32.dll} [00007FFF9643E222] Unknown function at  + $8382
(0000000000074CB5){COMCTL32.dll} [00007FFF96445CB5] Unknown function at SizeBoxHwnd + $9E5
(0000000000074BDF){COMCTL32.dll} [00007FFF96445BDF] Unknown function at SizeBoxHwnd + $90F
(0000000000074A13){COMCTL32.dll} [00007FFF96445A13] Unknown function at SizeBoxHwnd + $743
(00000000000748FF){COMCTL32.dll} [00007FFF964458FF] Unknown function at SizeBoxHwnd + $62F
(0000000000068B95){COMCTL32.dll} [00007FFF96439B95] Unknown function at  + $3CF5
(00000000000680EF){COMCTL32.dll} [00007FFF964390EF] Unknown function at  + $324F
(000000000000DF75){USER32.dll  } [00007FFF9FAAEF75] Unknown function at CallWindowProcW + $615
(000000000000D9EE){USER32.dll  } [00007FFF9FAAE9EE] CallWindowProcW + $8E
(0000000000219580){ExifToolGui_X64.exe} [0000000000D9A580] Vcl.Controls.TWinControl.DefaultHandler + $110
(00000000002198F1){ExifToolGui_X64.exe} [0000000000D9A8F1] Vcl.Controls.TWinControl.PaintWindow + $51
(0000000000219689){ExifToolGui_X64.exe} [0000000000D9A689] Vcl.Controls.TWinControl.PaintHandler + $89
(0000000000220910){ExifToolGui_X64.exe} [0000000000DA1910] Vcl.Controls.TWinControl.WMPrintClient + $80
(000000000000E944){ExifToolGui_X64.exe} [0000000000B8F944] System.TObject.Dispatch + $44
(0000000000211F50){ExifToolGui_X64.exe} [0000000000D92F50] Vcl.Controls.TControl.WndProc + $360
(0000000000219407){ExifToolGui_X64.exe} [0000000000D9A407] Vcl.Controls.TWinControl.WndProc + $967
(00000000002AB931){ExifToolGui_X64.exe} [0000000000E2C931] Vcl.ComCtrls.TCustomListView.WndProc + $E1
(0000000000414521){ExifToolGui_X64.exe} [0000000000F95521] Vcl.Shell.ShellCtrls.TCustomShellListView.WndProc + $61
(0000000000836DF4){ExifToolGui_X64.exe} [00000000013B7DF4] ExifToolsGui_ShellList.TShellListView.WndProc + $64
(0000000000211A52){ExifToolGui_X64.exe} [0000000000D92A52] Vcl.Controls.TControl.Perform + $32
(000000000021A496){ExifToolGui_X64.exe} [0000000000D9B496] Vcl.Controls.TWinControl.WMPaint + $166
(00000000002AE220){ExifToolGui_X64.exe} [0000000000E2F220] Vcl.ComCtrls.TCustomListView.WMPaint + $10
(000000000000E944){ExifToolGui_X64.exe} [0000000000B8F944] System.TObject.Dispatch + $44
(0000000000211F50){ExifToolGui_X64.exe} [0000000000D92F50] Vcl.Controls.TControl.WndProc + $360
(0000000000219407){ExifToolGui_X64.exe} [0000000000D9A407] Vcl.Controls.TWinControl.WndProc + $967
(00000000002AB931){ExifToolGui_X64.exe} [0000000000E2C931] Vcl.ComCtrls.TCustomListView.WndProc + $E1
(0000000000414521){ExifToolGui_X64.exe} [0000000000F95521] Vcl.Shell.ShellCtrls.TCustomShellListView.WndProc + $61
(0000000000836DF4){ExifToolGui_X64.exe} [00000000013B7DF4] ExifToolsGui_ShellList.TShellListView.WndProc + $64
(000000000021853C){ExifToolGui_X64.exe} [0000000000D9953C] Vcl.Controls.TWinControl.MainWndProc + $2C
(000000000013F096){ExifToolGui_X64.exe} [0000000000CC0096] System.Classes.StdWndProc + $26
(000000000000DF75){USER32.dll  } [00007FFF9FAAEF75] Unknown function at CallWindowProcW + $615
(000000000000D9EE){USER32.dll  } [00007FFF9FAAE9EE] CallWindowProcW + $8E
(0000000000088AAA){COMCTL32.dll} [00007FFF96459AAA] Unknown function at DefSubclassProc + $14A
(0000000000088789){COMCTL32.dll} [00007FFF96459789] Unknown function at DSA_Create + $1809
(0000000000088AAA){COMCTL32.dll} [00007FFF96459AAA] Unknown function at DefSubclassProc + $14A
(00000000000888A7){COMCTL32.dll} [00007FFF964598A7] Unknown function at DSA_Create + $1927
(000000000000DF75){USER32.dll  } [00007FFF9FAAEF75] Unknown function at CallWindowProcW + $615
(000000000000D8DC){USER32.dll  } [00007FFF9FAAE8DC] Unknown function at DispatchMessageW + $6EC
(00000000000206D3){USER32.dll  } [00007FFF9FAC16D3] Unknown function at SendMessageTimeoutW + $143
(000000000009FE64){ntdll.dll   } [00007FFFA17B0E64] KiUserCallbackDispatcher + $24
(0000000000000704){win32u.dll  } [00007FFF9F4B1704] NtUserDispatchMessage + $14
(000000000000D7C6){USER32.dll  } [00007FFF9FAAE7C6] Unknown function at DispatchMessageW + $5D6
(0000000000384623){ExifToolGui_X64.exe} [0000000000F05623] Vcl.Forms.TApplication.ProcessMessage + $133
(0000000000384698){ExifToolGui_X64.exe} [0000000000F05698] Vcl.Forms.TApplication.HandleMessage + $18
(0000000000384AEF){ExifToolGui_X64.exe} [0000000000F05AEF] Vcl.Forms.TApplication.Run + $EF
(00000000009BD114){ExifToolGui_X64.exe} [000000000153E114] ExifToolGUI.ExifToolGUI + $344
(0000000000016344){KERNEL32.DLL} [00007FFFA09C7344] BaseThreadInitThunk + $14
(00000000000516B1){ntdll.dll   } [00007FFFA17626B1] RtlUserThreadStart + $21

dgsjsj

version 6.2.9 works without error when opening.

FrankB

Hi,

I have 2 questions/suggestions.

1) Could it be that you have Language Dll's from a previous (old) version installed?

ExifToolGui_X64.DEU, ExifToolGui_X64.ENU, ExifToolGui_X64.FRA etc...

If yes, delete them and try again. If you want them, use the installer to install the matching language DLL's

2) What is the value of GUIStyle in the ini file?
- Ini file is located by default in %APPDATA%\ExifToolGUI\ExifToolGuiV6.ini
- Look in the section GUISettings for the line that begins with 'GUIStyle='
You can try to remove the line, or set it to Silver

[GUIsettings]
....
...
GUIStyle=Silver
....
....

Frank

dgsjsj

Quote from: FrankB on April 22, 2024, 05:28:58 PMI have 2 questions/suggestions.

1) Could it be that you have Language Dll's from a previous (old) version installed?

ExifToolGui_X64.DEU, ExifToolGui_X64.ENU, ExifToolGui_X64.FRA etc...

If yes, delete them and try again. If you want them, use the installer to install the matching language DLL's

2) What is the value of GUIStyle in the ini file?
- Ini file is located by default in %APPDATA%\ExifToolGUI\ExifToolGuiV6.ini
- Look in the section GUISettings for the line that begins with 'GUIStyle='
You can try to remove the line, or set it to Silver
1. Installed from ExifToolGUI_install_6.3.1.0.exe 16.9 MB
By default with all language packs.
Previously I only used version 6.2.9 (ExifToolGUI_X64) with exiftool in the C:\MyTools folder
2.C:\Users\USER\AppData\Roaming\ExifToolGui\ExifToolGuiV6
GUIStyle=
Changed to GUIStyle=Silver
Reinstalled version 6.3.1 without language packs and maps
C:\Users\USER\AppData\Local\Programs\ExifToolGUI
I launch the program from a shortcut on the desktop. The program runs without errors.
I am sincerely grateful for the prompt assistance.
All the best to you and good health.
 :)

FrankB

You're welcome. Thanks for your feedback!

Glad you got it sorted. For your info: I also changed the program, it will not run into an exception anymore if the GUIStyle is not valid. Will be in the next version.

Frank

QuoteAll the best to you and good health
Same to you.