This repository was archived by the owner on Jun 12, 2025. It is now read-only.
Multi touch support #8
Merged
Conversation
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
Contributor
Author
|
@residuum @deusanyjunior now that the pull request on the Common project was merged, I changed my branch to depend again on the Common repository. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Hi there,
I've added multi touch support to the app.
This was achieved by adding a new button to the main screen which leads to a dedicated multi touch fragment.
At the moment I've limited the maximal amount of simultaneous pointers to 8, however this limit could be increased if needed.
The OSC routing is in the format of
/touch1/for the first finger,/touch2/for the second finger etc..Please also have a look at the pd vanilla patch that I've updated to demonstrate this (see its bottom part with the touch messages routing).
The x/y values of each touch message range between 0 and 1 and a "touch up" message is represented by the value -1.
I had to make some minor non-breaking changes to the Measurement class in the Common project to make this work - if possible please merge the pull request for this feature in the common module first so that I can change the dependency to rely on the SensorApps version instead of my fork.
If there's any questions or comments about this - please let me know.
Cheers!
Tal