Repository navigation
Release notes
Profiles
A profile file renamed or copied by hand in the profiles folder could be left out of the manager's list yet still be applied when you signed in. Such a file is now named under the profile list with the reason; it is neither listed nor applied until it is put back under the file name the reason gives. Every change you make to a profile now acts on the file it was read from. Two profile names the manager treats as different can no longer end up sharing one file; saving a new profile never writes over another file. Profiles saved by earlier versions keep working as they are.
A profile file edited by hand to drop the format it is in is now named as unreadable rather than guessed at; so is one that no longer says whether an application was running.
Restoring
When a profile held two programs from one packaged application, a restore could place one window for both of them, so it could end up where the other program belonged. Each window now goes to one entry only, preferring the entry that names its program exactly; a program left without a window is reported as such.
Installing and updating
When setup closes a running copy of ScreenState before replacing it, it now recognises that copy by its full path in the install folder. A different program that happens to share the name is left alone.
The update check now opens only secure (https) links in your browser. A release pointing anywhere else is passed over and noted in the log.