Change order of removeView and onDismiss call#177
Merged
xiphirx merged 1 commit intoKeepSafe:masterfrom Jul 16, 2017
Merged
Conversation
Collaborator
|
Nice catch! Thanks for the PR! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The value
userInitiatedofTapTargetView.Listener.onTargetDismissed(TapTargetView, boolean)was alwaysfalsewhen I tried TapTargetView in my project.Looking at the code it seems like it is supposed to be always
trueexcept when the removal of the view is not triggered by the end of an animation (which was triggered by a user interaction).Changing the order of the
onDismiss()prevents the removal of the view from triggeringonDismiss(false).