Main Menu

Recent posts

#11
General / Keyboard navigation in File Wi...
Last post by axel.hennig - Today at 06:12:21 PM
I have the feeling that this issue is related to the (already fixed) Scrolling issue.

When beeing in a folder containing more images than actually fit on the screen, having the first image selected and then pressing the "end" key (opposite of "Home" key and on my German keyboard it would be "ende" compared to "pos1"), IMatch jumps to the last image, but it is not fully visible (see screenshot).

Pressing "end" again or using the "arrow" keys does not help.

Using the mouse helps or clicking into the scrolling-bar, but not just using the keyboard.

sc1.jpg
#12
Kann mir ehrlich gesagt nicht vorstellen, dass ACDSee einfach einen Ordner löscht/verschiebt...
Was ist denn bei dir der Unterschied zwischen Quell- und Fotoordner? Wenn beide identisch sind, dann mach einen Restore des Fotoordners mit den Bordmitteldn deines Betriebssystems und dann in IMatch einen Relocate auf den wiederhergestellten Ordner.
#13
General / Re: Viewer Opens Slow
Last post by Mario - Today at 01:47:49 PM
Sorry, I forgot. Just wanted to clean up some loose ends.
I will add more logging to the next release.
#14
Aus unerfindlichen Gründen ist mein ursprünglichen Fotoordner verschwunden. Vermutlich ist das durch die testweise installation von ACDSee passiert? Alle Bilder sind off-line. Die Relocate Funktion ist nicht zur verwendenm da der Quellordner nicht mehr existiert. Mein Fotoordner ist gesichert. Kann ich die Fotos neu einlesen, oder?
#15
General / Re: Viewer Opens Slow
Last post by axel.hennig - Today at 11:59:10 AM
Quote from: Mario on Today at 10:14:20 AMI've added more logging in the 2025.2.2 release.
I think you've mentioned that additional logging was added in 2025.2.4, which was released 19.03.2025.

My two posts above (post 1, post 2, 19.03.2025, IMatch 2025.2.4) should have the additional logging and you've already replied to both.

Also Mees has replied with the additional logging (his post with additional logging) and you have also already replied to his post.

Do you need anything else? I'm still experiencing the slow opening.
#16
General / Re: Viewer Opens Slow
Last post by thrinn - Today at 10:33:38 AM
I did not experience any issues. Do you mean Axel?
#17
General / Re: Viewer Opens Slow
Last post by Mario - Today at 10:14:20 AM
@Mees and @thrinn

Can you still reproduce this? If so, switch to debug logging, open the Viewer. If it's still slow, use Help > Support > Copy Logfile, ZIP and attach. 

I've added more logging in the 2025.2.2 release.
#18
Fixed for the next release, thanks.
#19
Mario, it was Tag XMP::xmpMM\PreservedFileName\PreservedFileName\0.

I performed another test, using a single file that already had that tag set, and when I ran my Template on it, the file did not become pending for writeback.

So I repeated the test, this time with a contiguous range of 9 files, 4 of which lacked the PreservedFileName Tag, and the other 5 having it already:

    1.) 72982
    2.) 75251
    3.) 75253
    4.) 75257 <=
    5.) 75261
    6.) 75263 <=
    7.) 78332 <=
    8.) 75268 <=
    9.) 75270

I selected all 9, ran my MD Template on them, and all 9 became pending for write-back.  But only the 4 that were actually updated (and now had a new value in PreservedFileName) showed the tooltip:

    Screenshot 2025-04-02 162027.png

...and the other 5 (although also having an active pen icon), did not put up a tooltip when hovering over the pen.

The next Database Diagnostics mentioned all 5 of those OIDs:

Checking Metabase:
        should be not pending: [72982]...
        should be not pending: [75251]...
        should be not pending: [75253]...
        should be not pending: [75261]...
        should be not pending: [75270]...

...and afterwards, the 9 files were now in the correct state (with only the 4 of them needing writeback).

I turned on Debug Logging before running the MD Template, and can send that, and the Diagnostics log, if needed.
#20
Which tags with which options does your template update?

I tried to reproduce this with a template that sets headline and hierarchicalSubject with the option "Insert only if tag is empty" and when I applied the template to a file with existing headline / keywords, the pending state was not set.