RFC: Input handling #219
Draft
RFC: Input handling #219
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
Copy rfc/0000-template.md to rfc/0000-my-feature.md
Started summary
Motivation
…e content to motivation
|
@DerKarlos Hi! Are you still interested in pushing this forward? :) |
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.
Define the needed inout handlers, and functions according to maplibre-gl-js.
Create and document the demo input handlers (keys, mouse, touch) and separate them in an extra Rust crate.
Add a set/interpolate API to the map code for the handlers.
Check, if/what variations of winit, we need
💻 Examples
🚨 Test instructions
Check the maplibre-gl-js code, what input functions are exprected.
Use the maplibre-gl-js UI and check if maplibre-rs has the same behaviour
Use the exampel handler check if a variation is possible and the API documented.
✔️ PR Todo