Open
Conversation
This will help when handling gestures with conflicting areas
Mrcubix
added
bug
This is preparation for the Gesture debugger in the UX
Owner
Author
|
TODO : Figure out what's broken with inheriting from GesturesHandler |
… with broken .NET behaviors.
Add some checks to the installer to make sure we don't throw on setup with broken .NET behaviors
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.
It's time to rework or rewrite some of the gestures to make them not only easier to test & debug, but to also properly work when multiple gestures's ares conflict with each others.
It's also time to write some form of documentation, outside of the code itself, on how each of these gestures work in my lib.
I am fully aware that they still won't be properly implemented, but they seem to match all the behaviors i've tested on touchpads, mobile devices.
The property serialization rewrite will then soon follow, allowing users to use Bindings with multiple properties associated.
Closes #8