-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
release 1.3 android template small bug #68
Comments
Now, I keep correcting myself. I added GetGestureType and made it work properly. I see that bool IsGestureDetected(void)
} Maybe it is a good idea to keep the trace logs on user events, but only on the debug version. working sample: |
Hi, I'm currently working on that at #67 IsScreenTouched() from 1.2 already checked TAP input so detecting the scene switch worked fine one per touch. But now in 1.3 IsGestureDetected() returns true when any type of input is detected (look at gestures.h Gestures enum type data, line 56). You can improve the code just checking GetGestureType() return value. If you see IsGestureDetected() declaration, it just checks if GetGestureType() is not GESTURE_NONE, so you are doing the same thing twice. |
Hi @dmalves! Gestures module has been reviewed in develop branch for raylib 1.4. Thanks @victorfisac for taking care of this issue. I just merged your pull request #67 and commented it. |
IsScreenTouched() from 1.2 is used where I guess IsGestureDetected() from 1.3 should be used.
affected file:
https://github.com/raysan5/raylib/blob/master/templates/android_project/jni/basic_game.c
after that compilation to android compiles just fine and the app runs. I had to add
InitGesturesSystem(struct android_app *app);
and
void UpdateGestures(void);
to make it work, but still the game screen jumps from TITLE to GAME to END to TITLE again very fast while I hold my finger on the tablet screen.
I just modified a few lines:
https://gist.github.com/dmalves/de34b9a56be2c9d5ebb0
How can I detect a single screen tough?
The text was updated successfully, but these errors were encountered: