| Summary: | SDL_HINT_ANDROID_SEPARATE_MOUSE_AND_TOUCH doesn't work after init | ||
|---|---|---|---|
| Product: | SDL | Reporter: | Anthony @ POW Games <ant> |
| Component: | video | Assignee: | Ryan C. Gordon <icculus> |
| Status: | RESOLVED WORKSFORME | QA Contact: | Sam Lantinga <slouken> |
| Severity: | major | ||
| Priority: | P2 | CC: | icculus |
| Version: | 2.0.4 | ||
| Hardware: | All | ||
| OS: | Android (All) | ||
|
Description
Anthony @ POW Games
2016-01-07 17:48:45 UTC
(In reply to Anthony from comment #0) > SDL_androidtouch.c sets a callback in Android_InitTouch if > SDL_HINT_ANDROID_SEPARATE_MOUSE_AND_TOUCH is set. No, it sets a callback that is called right away with the initial value of that hint, and then again any time the hint is changed. Is this not working? --ryan. It appears to be working perfectly now (after I've slept and returned to the test code). I'm trying to get more information about the right mouse button quit bug and was sure I had found a problem. Very sorry Ryan, forgive me. I just found the source of my confusion. I was calling:
SDL_SetHint("SDL_HINT_ANDROID_SEPARATE_MOUSE_AND_TOUCH", "1");
I didn't think it would matter - my lack of understanding how SetHint works.
(In reply to Anthony from comment #3) > I didn't think it would matter - my lack of understanding how SetHint works. No worries! --ryan. |