Bug/touchscreen launch objects

[johnshaughnessy]

Might fix #4036

[yakyouk]

Would it make sense to change this to be time-based instead of frame-based?
On a poorly optimized scene and/or an older device, responsiveness might be bad - tho arguably, even at 15fps, 8 frames would be just half a second.

[johnshaughnessy]

@yakyouk

Would it make sense to change this to be time-based instead of frame-based?

I think the correct behavior depends not on time or app-aware-touchscreen ticks, but on having two (worker-thread) physics world ticks with the cursor in the same spot. So the correct fix is probably to have the countdown tied to those physics world ticks instead of the app-aware-touchscreen's ticks.

This PR is not the correct fix, but it is not any more harmful than what we had before. It's bad because it avoids the problem instead of actually solving it.

[takahirox]

I tested with this change on Android Chrome, iOS Safari, and iPad. I confirmed that this change improves a lot. I still rarely throw objects but very rare.

Downside of this change may be response time can be a little bit slow. But slow response should be much better than unexpectedly throwing objects.

We might want to fix the root issue at some point, but this workaround is easy and worth. I would like to vote for going with this change so far.