There are two problems with SettingsConverter that I could not fix.
The tool changes some skin settings or AlbumObject settings for the current project. There is a possibility that jAlbum will overwrite these changes with its cached settings. To prevent this, in the instructions I specify that you must open the project immediately before running the tool and close it immediately afterwards.
1) When the tool starts, I want to verify that there are no unsaved project settings. If there are unsaved changes, the tool should terminate. I checked
but this always returns true, even if the project has just been opened. Is there a way to detect if there are any unsaved changes?
2) When the tool finishes, I want to automatically close the project. Is there any way I can do this?
In one of my tests, after running SettingsConverter, I closed the project. jAlbum asked me if I wanted to save the project changes and I replied "Yes". After I re-opened the project I noticed that one of the converted settings had reverted to its previous value. My assumption was that jAlbum saved the original value.
So, to be safe, I want to avoid jAlbum and SettingsConverter from tripping over each other. Without knowing the internals of jAlbum, I am being extra cautious.
I see. Thanks for providing this. I can't know what triggered the save changes warning. If you want to know, set debug level to FINE, then inspect jAlbum's system console after such a message has been triggered. It will then print what settings differ. Making changes via jAlbum's API's like you do should be fine.