Tagging Photos

[tim@timellis.me.uk]

So I load the tracks to show the route on the map
Then I load the photos in the photo tab - lets say it shows 40 taggable pictures
I set "show taggable photos only" and select all of them.
I click "Tag Photos"
It now shows 25 tagged photos and 15 taggable
The15 untagged photos are still showing as taggable but clicking on "Tag Photos" has no effect whether just one or multiple photos are selected.
If I quit TimeAlbumPro, restart it, reload the map, reimport the photos, select the 15 taggable photos and select "Tag Photos" it tags 13 of them, leaving 2 untagged - again, any attempt to tag them fails.
Quitting and restarting TimeAlbumPro a third time finally allows me to tag the remaining photos.

Is there a better workflow that allows me to tag all the photos in a single action, or at least without needing to continuously restart TimeActionPro (and so redownload all the offline data each time?)

[routeconverter]

That sounds like a bug. Could you use Help/Send error report... so I can have a look at the logs?

[tim@timellis.me.uk]

Trying to send an error report - it asks me to log in, but doesn't accept the username/password I used to log on here?

[tim@timellis.me.uk]

Trying to send an error report - it asks me to log in, but doesn't accept the username/password I used to log on here?

I registered as Tim_Ellis and sent the report...

[routeconverter]

I've received the report but didn't find time yet to look into it.

[tim@timellis.me.uk]

Thank you

[routeconverter]

Found it, thanks for the error report — it had exactly the evidence I needed.

The bug: when tagging a batch of photos, each tagged photo pushes a table-update notification from a background thread instead of the UI thread. That collides with the profile/elevation chart repainting on the UI thread at the same moment, corrupting its internal data and throwing an exception. Once that exception hits, the batch silently stops making further progress — the remaining photos stay "taggable" with no error shown. It's timing-dependent, which is why it doesn't always fail at the same photo, and why restarting sometimes lets you tag a few more before it happens again.

Fixed now — the update is properly deferred to the UI thread, and I added a regression test around the fix. It's already in the rolling prerelease build: https://releases.routeconverter.com/prerelease/ — grab that if you want the fix now, otherwise it'll land in the next stable release and I'll post here when it's out. In the meantime, if you hit the same stall again, tagging in smaller batches (~10-15 photos at a time) should avoid triggering it, or just retrying "Tag Photos" a couple more times on the leftover photos will get there without a full restart.

Thanks again for reporting it and sending the logs.