The plugin adds a custom command to open a dialog showing file's metadata using ExifTool.
Download from the Github repo: DirectoryOpus-ExifTool-Dialog.
Please read the README.md How to use section.
1 Like
Nice !
I already had ExifTool installed.
This made that far more useful in about five minutes.
Edit Note: There is a new ExifTool icon SVG here .
1 Like
Amazing.
Thank you for the link to the icon.
I have updated the plugin.
Changes:
- Add an icon to the dialog
- Don't show the ExifTool version
- Make the dialog resizable
- Use the FILE input parameter instead of a selected file.
If you used a previous version, you need to change the command configuration a little bit, Please check the screenshot in the README.md How to use section.
Got It !
The new version works fine.
It is only a five minute adjustment from the original version.
It would be good if someone is able and willing to do some work on the icon so that it works better in Dark Mode.
Dark mode works fine though in Polar Goose's window title.
Edit: I just got the CLICK HERE: Link your account for priority support bug again. 
Double Edit: The ExifTool internal icon works well enough in Dark Mode.
Sorry,
There is a small problem with the new version that was avoided in the original version.
If multiple files are selected, the program freezes.
I'd show more detail, but I just got a DOpus crash log .
I'm able to show at least that part now.
I'll see if I can get both the window that freezes and the crash log.
I'll send this for now as I still can.
No Luck !
The crash log is too large to submit.
It really isn't that bad, exiting Directory Opus clears it.
It is caused by selecting multiple files in the new version.
I'll see if I can get a screen grab of the error as it occurs.
Nope, I need a computer restart to clear it.
Here is the error as it happens.
I don't know yet if a @firstfileonly would fix this or not.
I had to do a restart to get this again.
Edit Note:
Hindsight is always perfect. Closing the pop up ExifTool dialog clears the error .
@PolarGoose I still like your Script ! Thanks !
Sorry, I think I just trashed your thread.
Maybe start a new one and delete this one ?
Thank you for the bug report. Very interesting why it can happen.
I have checked that if you use OpenExifToolDialog FILE {filepath}, then DOpus always passes one file, even if you select many files. Thus, selecting many files shouldn't cause any problems.
Can it be that the problem is because you use it for a specific file?
Sorry, I think I just trashed your thread.
Maybe start a new one and delete this one ?
Haha, no it is not needed 
Don't worry.
Does it happen with any files? For example, what if you select several text files?
Yes, It also happens with text files.
@Jon @Leo I have the crash dump, but it is 48.4MBs.
I can upload it to a personal web domain and give you a link to it if that would be useful.
Unfortunately, the file is too large for the built in compress and send.
Nuts that it would be this large !
Yes, indeed, I have managed to reproduce it on Windows 8. It also reproduces on Windows 11 24H2
I have recorded the demo:
I print in the debug log the file that DOpus passes to the script.
It is not related to my script functionality because it happens even if I comment out code that calls ExifTool.
@Leo,
Hello, could you please take a look at this issue?
Good to know I'm not nuts !
I have found what is happening:
Directory Opus automatically shows the File Function progress bar when a command is being executed with a file as a parameter. However, it seems that on Windows 8 and 10, this progress bar gets focused and sends the main ExifTool dialog in the background. That is why I didn't see this problem on Windows 11 because the ExifTool dialog is shown on top of this progress bar dialog. And because the ExifTool dialog is blocking, you can't do anything with this progress bar dialog because it waits for the ExifTool dialog to be closed.
To avoid this issue, the workaround is to use @noprogress attribute:
@noprogress
OpenExifToolDialog FILE {filepath}
I have updated the Readme file in the repo.
@David, could you please check if this workaround helps?
1 Like
Yes !
Adding @noprogress seems to have stopped the problem.
Thanks !