Fixed Keyboard not showing second time.#24
Open
marco-calautti wants to merge 1 commit intomaximcus:masterfrom
Open
Fixed Keyboard not showing second time.#24marco-calautti wants to merge 1 commit intomaximcus:masterfrom
marco-calautti wants to merge 1 commit intomaximcus:masterfrom
Conversation
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
1 participant
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.
I had this issue in a project I am working with. The issue is essentially the fact that the bind occurs only in two cases: Focus (which is the first time the textblock is clicked), and touchdown. However, if the textbox does not loose focus, and one clicks on the textbox with the mouse, instead of using the touch screen, the keyboard will not popup.
This pull request fixes this issue by also binding the PreviewMouseDown event.
According to MSDN, we should not override MouseDown, as textboxes have their own behavior for that.
This fix referes Issue 20