Skip to content

Conversation

@ksperling
Copy link

This can happen when a DOWN event is triggered in the quickreturn area, and the finger then moved out of that area without triggering a drag (e.g. by moving vertically first and then across). If the menu is then closed in some other way (e.g. back key) the CustomViewAbove remains in mQuickReturn == true state and blocks all touches to the main content, making the app appear unresponsive or crashed to the user.

This can happen when a DOWN event is triggered in the quickreturn
area, and the finger then moved out of that area without triggering
a drag. If the menu is then closed in some other way (e.g. back key)
the CustomViewAbove remains in mQuickReturn == true state and blocks
all touches to the main content.
@trashkalmar
Copy link

This really helps, thank you!

@xu6148152
Copy link

yeah, this bug I have encountered
and I merge this commit to my library SlidingMenu

@ksperling

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants