diovudau
diovudau
At the moment it is not possible to let nsmd run under an url of the users choice. @spotlightkid researched the following * liblo with IPv6 does not work reliably....
At the moment there can only be one GUI for an instance of `nsmd`. While this may seem reasonable at first glance it prevents usecases like specialized helper tools, such...
At the moment there is no programmatic way parse a system for installed NSM-capable clients. Internal and IRC discussions about this have been going on for some time, hereby transferred...
Loading or closing existing session with many clients can take some time at the moment. But there is apparently no reason why client A needs to wait for client B.,...
All OSC messages starting with /nsm/gui/ were previously undocumented. This section of the API needs some work and then official documentation in the API document. This has nothing to do...
Here a place to review and discuss packages in distributions and the process of getting them included. Especially to comply with distributions standards, if there is anything wrong. Also good...
There is no testing and quality assurance at the moment. Volunteers are needed that have experience in writing tests. This is only for the daemon, not for any GUI.
AFAIK this is not a regression, but needs testing. When a session is currently loading and takes very long, for example because the 5 second timeout is waiting for a...
When a client is removed from a session it leaves data behind. This is both needed and undesired. * It is needed because a removed client is not a final...
As wished by @unfa and https://github.com/original-male/non/issues/287 and others Proposed solution for the requested behaviour: A client that can be added to a session which has slots for various NSM events....