-
Notifications
You must be signed in to change notification settings - Fork 236
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
Request follow caret #378
Request follow caret #378
Conversation
… interrupts logicality of code's order
@@ -169,13 +169,14 @@ | |||
.orElse(otherNavigation).ifConsumed((b, e) -> b.view.clearTargetCaretOffset()) | |||
.orElse(verticalNavigation) | |||
.orElse(copyAction) | |||
.orElse(charPressConsumer); | |||
.orElse(charPressConsumer) | |||
.ifConsumed((b, e) -> b.view.requestFollowCaret()); |
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.
Maybe these last two lines should be swapped? Shouldn't make a change in observable behavior, but when charPressConsumer
consumes an event, we expect a KEY_TYPED event, and we requestFollowCaret
there.
Updated in light of your comment. |
👍 |
Since that's now a public method... we should add some javadoc to explain On Oct 6, 2016 5:18 PM, "Tomas Mikula" notifications@github.com wrote:
|
I amended the commit, but it seems to have shoved the two commits into one. Thus, |
Should fix #101, but I'm not sure if I implemented it correctly.