Closed raresn closed 2 years ago
That one should be easier to solve than your last one. :wink:
I introduced these zones so that system gestures — like dragging upwards from the very bottom on iOS or the "back" gesture on Android – don't interfere with user interface elements that are positioned closely to the edge of the screen.
You can deactivate that by calling Starling.current.touchProcessor.discardSystemGestures = false
.
Alternatively, you can also change the size of those regions anytime via the setSystemGestureMargins()
method on the same class.
Smart! :) We resolved this bottom edge problem on ios by adding a black 20 px bar at the bottom of our app, since we have elements right at the very bottom of the screen! :) So now we have a black bar, and on top of that we have elements that need interaction.
The discardSystemGestures = false works! Thanks a lot!
We noticed our app doesn't catch touch events on the first ~20 pixels from the bottom, and we checked if we had the latest Startling. We didn't. :) We updated to 2.7 and now the left side doesn't catch touch either. So the only difference is switching the Starling swc from 2.5 to 2.7, and:
Any clue what we are missing to have the entire viewport clickable? (the viewport size is correct)