Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes for version 1.2.164 #71

Merged
merged 2 commits into from
Oct 11, 2019
Merged

Fixes for version 1.2.164 #71

merged 2 commits into from
Oct 11, 2019

Conversation

AGulev
Copy link
Contributor

@AGulev AGulev commented Oct 11, 2019

We added multi touch feature for HTML5 in 1.2.164

@AGulev AGulev requested a review from britzl October 11, 2019 17:01
@@ -96,7 +96,7 @@ Gamepad Triggers
Touch Triggers
: Single-touch type triggers are available on iOS and Android devices. Single-touch type triggers are not set up from the Touch Triggers section of the input bindings. Instead **single-touch triggers are automatically set up when you have mouse button input set up for `MOUSE_BUTTON_LEFT` or `MOUSE_BUTTON_1`**.

: Multi-touch type triggers are available on iOS and Android devices in native applications (ie not HTML5 builds running on a mobile device). They populate a table in the action table called `touch`. The elements in the table are integer-indexed with numbers `1`--`N`where `N` is the number of touch points. Each element of the table contains fields with input data:
: Multi-touch type triggers are available on iOS and Android devices in native applications. They populate a table in the action table called `touch`. The elements in the table are integer-indexed with numbers `1`--`N`where `N` is the number of touch points. Each element of the table contains fields with input data:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we mention that it works in HTML5 as well? Or remove the "in native applications" text?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, you right.

@AGulev
Copy link
Contributor Author

AGulev commented Oct 11, 2019

I've made fixes

@britzl britzl merged commit 31faea4 into master Oct 11, 2019
@britzl britzl deleted the 164 branch October 11, 2019 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants