Great. I might update the tool to show more information when it completes, so if no duplicate is found you don’t need to look in the system console.

The chance are you will remember about duplication of base file names and not need to use it in new projects.

I left excluded images in the checklist for several reasons. It could be one is used as a theme image and the other as part of the album, I don’t know what effect that would have. A user may have temporarily excluded the object, but intends to use it later on. A skin may have a script function that uses getDescendants(), that can include excluded objects.

By checking all files a user can always decide if a file does need renaming or not. But if the change you made is what you want go for it.

I normally include a start message for two reasons, so the users knows the script is running and it gives them a chance to exit without running it, should they have accidentally picked the wrong tool. I also usually have a script completed message, some of my tools can take a while to run, for exemple making a video from the images in a folder/project.

Glad you have a solution that works for you.

I’ll have a think about that, I could ignore RAW & JPG, they should only really appear if jAlbum has processed the RAW files. The problem is I’m lazy and checking for all RAW file formats would be tedious.

…

OK. I’ve had a think and I will ignore excluded objects, it is the path of least resistance.