Redundant handling of mouse and touch events on mobile platforms

Not a support question, but wanted to make sure what I found was easy for others to find if they have the same problem. After spending a lot of time trying to figure out why my touch events stopped working on iOS after I upgraded from Urho3D 1.5 to Urho3D 1.8 alpha, I found out that is was related to my code being setup to run on both desktop and touch platforms. Apparently in SDL2.0.4, iOS (and presumably Android), generate mouse messages for touch events by default (I don’t think that was true in the earlier version of SDL that Urho3D 1.5 used). In my application, I run the same code on Windows and iOS, so I had both mouse and touch event handlers, and they started both getting called on iOS, which caused a lot of bad behavior. I found this link that talks about the problem.

So for me, the fix was to call the following in my initialization code. Even though the hint appears to be specific to Android, it fixed my problem on iOS as well.

#include <SDL/SDL_hints.h>

//In initialization code

1 Like

That hint has been removed since SDL 2.0.10 and replaced by two new hints. See SDL 2.0.10 release notes and also below changes in Urho3D code base.

Are you suggesting we need the same hints to be applied for iOS and tvOS?

Don’t bother with the releases. They’re old and buggy and master has more features. 1.8 is fine I think. Also don’t forget that android can use a mouse via usb-otg. I like this feature, but you don’t have to support it

I’m assuming that it is needed for iOS, but not sure about tvOS (does tvOS support touch?). I added an extra defined(IOS) as shown below, and it fixed the problems I was seeing.

#if defined(__ANDROID__) || defined(IOS)
    // Prevent mouse events from being registered as synthetic touch events and vice versa
#elif defined(__EMSCRIPTEN__)
    emscriptenInput_ = new EmscriptenInput(this);

As the next poster pointed out, I think setting these values to zero might not always be what you want, but it is probably a reasonable default (and matches the old behavior of Urho3D, so should avoid breaking apps like it did for me). In my application, I handle mouse events and touch events separately, which I thought I needed to do to handle multi-touch when it is available, but maybe if you set SDL_HINT_MOUSE_TOUCH_EVENTS to 1, then the mouse works like a single touch? In any case, I’m assuming that you could override these hints anywhere in the setup code that is called after the code above.

Yeah, after making that comment, I also realized I might have made mistake by putting tvOS in the same line but then again I have not been following Apple closely recently.

Care to submit your one line change above as PR?

It might take me a few days, but I’ll try to submit a PR. I need to learn Git first, my total knowledge to date on it was just enough to clone the repository.