Not an issue for the majority of actively-maintained skins, which use a compiled UI, but in a skin with an old-school, interpreted onload.bsh, the contents of the SkinModel.java file are ignored. The Zigzag skin is a prime example - there are three booleans that should default to true, but they don't.
I'm fairly certain this used to work, but I can't pin down which jAlbum version caused it to stop working.
Edit: This appears to fail only in Windows, which points to a Java version problem (Windows is using Java 9, macOS is using Java 8).
Thanks for reporting. What I actually observe on Windows 10 with Java 9 is that it takes two consecutive skin loads (not reloads) for the changes in SkinModel to kick-in. I currently don't know why that is.
I just replaced headless-settings.jap by the SkinModel.java file in my un-compiled skins.
Should I go back to the old situation with the headless-settings.jap?
I recommend sticking with SkinModel. It's more powerful as it sets default types for your variables too.
No need. The bug in the old version simply prevented the script from running at all.
If you were able to use the old version successfully, then the output generated would be identical to that generated by the new version.