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.
Beware : quite experimental and not fully tested.
In particular, the current version creates a lot of
And seems to increase drastically the compilation time.
This replaces
event.device().unwrap().num_touches()
by another approach, using the fact that each touch sequence is associated to a unique (and constant) sequence. Hence we can useevent.event_sequence().as_ptr() as usize
to distinguish different touches and follow it.This prevents any zip-zap when there are multiple fingers on the screen when
Draw with Touch
is enabled.Apparently, the
EventSequence
type is touch specific (so maybe it would be possible to add this into #672 ? Though I don't know if you'd segfault if the function is called on a non touch event).