Open
Conversation
(this was wrong in the source material/docs)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Many clients expect INDI drivers to publish a DRIVER_INFO vector that includes a DRIVER_INTERFACE element. This DRIVER_INTERFACE is a bitwise OR of the values listed on this page, and advertises what kind(s) of device the driver represents.
This PR adds a new enum in device.py that encodes these interface values for convenience.
Note: I'm not quite sure if this is where this should go. I couldn't really think of anywhere better, but if there is a more optimal location for this definition to live, I'd be happy to move it.