Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Persist Control mappings for Remote Input and TCP (and possibly elswhere) #80

Open
erict-powersoft opened this issue May 15, 2024 · 2 comments
Assignees

Comments

@erict-powersoft
Copy link
Contributor

erict-powersoft commented May 15, 2024

It would be nice if the control mappings for special controls, which are set up in Remote Input Server, as well as SPORTident / TCP, can be combined. I cannot imagine a use-case where they would be different.

Secondly it would also be nice if the last setup is retained for any future event - our control IDs are always the same so every race we need to set the control mappings to the same values. These settings should be retained in Local Settings.

Thirdly, it would be nice if the control mappings could be made available through the info server.

@erikmelin
Copy link
Contributor

I agree that having them consistent and persistent within a event seems reasonable.

Saving them as a local setting I am not so sure about. If you know what you are doing its fine, but if you are not so familiar you could accidentally set something bad. Exposing them externally seems less important until there is software that will configure the SI units for a given event automatically and remotely.

@erikmelin erikmelin self-assigned this Oct 6, 2024
@erict-powersoft
Copy link
Contributor Author

erict-powersoft commented Oct 7, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants