Update to pyspacemouse 2.1.0 - #82
Open
peter-mitrano-ar wants to merge 1 commit into
Open
Conversation
With 2.1.0, there is we can specify the HID_Z_UP convention which should be equivalent to the previous code.
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.
Since the new major version 2.0, the API for opening by path has changed.
And specifically with 2.1.0, there is we can specify the HID_Z_UP convention which should be equivalent to the previous code.
Currently, the version of pyspacemouse is unpinned, meaning that anyone who tries to set up the dev environment now and use spacemice by path will silently have problems, because the spacemouse that gets open could be the wrong spacemouse!