@trixie
Quote:
I find it rather worrying than an application should be able to unregister another application. This can be fairly dangerous. Imagine that an app continuously accesses a prefs dictionary, an operation that - after unregistering by a third party - will stop working with unpredictable results.
Registered apps rely on staying registered until unregistering themselves from the system. A third-party unregistration is an illegal operation IMHO. If the Application Library supports it, then we have a design problem that should be addressed.
As Andy I think such kind of tools is for experimented users knowing what they are doing. Moreover such kind of utilities always existed on AmigaOS just to circumvent "lacks" of the OS (automatic cleaning of a crashed task, including closing of locked/opened resources such as windows, files, etc.). If you remove unregistering then you should also remove UnlockScreen() because another task may unlock the screen.
Moreover any application should check return code and react accordingly, in the application.library unregistering an already unregistered application should return an error code (which it seems to do according to the autodocs).
SysMon is a very useful tool for programmers (IMHO).