Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
apps:categories:nsm [2013/06/17 18:12] – Corrected spelling of "supersedes" rockhopper | apps:categories:nsm [2014/01/28 22:26] – Minor clarification rockhopper | ||
---|---|---|---|
Line 11: | Line 11: | ||
* Fully compatible with apps that have built-in NSM support regardless of their audio backend (be it JACK, ALSA, PulseAudio, etc.) | * Fully compatible with apps that have built-in NSM support regardless of their audio backend (be it JACK, ALSA, PulseAudio, etc.) | ||
- | * Not compatible with apps that have support for other session | + | * Not compatible with other session |
* Limited compatibility with apps without session manager support (via nsm-proxy) : | * Limited compatibility with apps without session manager support (via nsm-proxy) : | ||
* Some apps are programmed to save their current state when they receive the “SIGUSR1” Unix signal, and NSM is able to send this signal to such apps. On receiving this signal, apps may then open a save file dialogue or save their state to a default file location. The user may need to load this state file manually after a session is restored | * Some apps are programmed to save their current state when they receive the “SIGUSR1” Unix signal, and NSM is able to send this signal to such apps. On receiving this signal, apps may then open a save file dialogue or save their state to a default file location. The user may need to load this state file manually after a session is restored |