You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any possibility to have per application settings, depending on the window with focus? This is present in the Windows version of the software, so it would be nice to have it in Linux as well.
The text was updated successfully, but these errors were encountered:
Currently there's no provision for per-application settings. I'm marking this as a feature request.
The reason why I never supported any per-application settings is that ideally I think the Right Thing to do is to send the same events to all applications, and let the applications decide what to do with them. They should have their own 6dof configuration (as some do) to define button actions in the app itself, sensitivities and so on.
However I realize that not all applications bother to do that, and it would be useful for spacenavd to be able to differentiate between applications and change some things accordingly, which is part of the reason I added a new command in the latest protocol revision for applications to identify themselves upon connecting to the spacenavd socket. I'm opposed to using focus for this. Having a window system running at all, and interacting with it if it is, has always been an optional value-added part of the spacenavd functionality, and any such core feature should work at the protocol level.
If anyone is interested in implementing this, please contact me to discuss implementation details first.
If someone finds it useful, I solved this by keeping multiple/separate spnavrc files and re-starting the spacenavd with different config file as needed.
Is there any possibility to have per application settings, depending on the window with focus? This is present in the Windows version of the software, so it would be nice to have it in Linux as well.
The text was updated successfully, but these errors were encountered: