Added mouse button aliases #579
Open
Conversation
This file contains 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
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.
This might be a personal preference, but I usually have
MouseButtonimported, which would make it easier to doMouseButton::Left, compared to importingglfw::MouseButtonLeft.Additionally, this is also sliiiightly "safer" to use, as if someone forgets to import
glfw::MouseButtonLeft, then matching on aMouseButtonand havingMouseButtonLeftin a match arm, that would only produce a warning. While forgetting to importMouseButtonwhen usingMouseButton::Left, would cause an error.I can refactor some of the
MouseButtonLeft(and friends) doc references, to instead point toMouseButton::Left(and friends), if that is desired?