-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed an issue of content taps being cancelled by the drawer tap recognisers. #57
Conversation
0da91e5
to
f276167
Compare
3bfff69
to
b411be3
Compare
bda2f00
to
bffcdcb
Compare
bffcdcb
to
45b6712
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only a nit
return false | ||
} else { | ||
return true | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
return (subview is UIControl).isFalse
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's no isFalse
in DK IIRC.
The two tap recognisers installed by DrawerKit, if enabled, would cancel the delivery of touch events to the content view by default. This causes problems with at least
UITableView
, whose selection mechanism relies on these events.This branch also enables controls within the drawer content to be interactive, even if the drawer is not fully expanded.