Skip to content
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

Keyboard API Support / Windows 10 onscreen keyboard doesn't auto appear when UITextField gains focus #332

Closed
ehren opened this issue Jan 21, 2016 · 2 comments

Comments

@ehren
Copy link
Contributor

ehren commented Jan 21, 2016

The onscreen keyboard fails to appear when a UITextField gains focus with the TextFieldsViewController in the WOCCatalog app (or any app).

I'm running Windows 10 Pro on a Dell Venue 11 Pro (5130).

I've selected the Devices->Typing setting "Automatically show the touch keyboard in windowed apps when there's no keyboard attached to your device" (and this works for standard applications like Firefox). Maybe the universal WOCCatalog app doesn't count as a "windowed app"?

In either case, it would be nice if the onscreen windows keyboard responded to the UITextField gaining focus (via either touch or call to becomeFirstResponder). It would also be nice if it dismissed in response to e.g. a call to [self.textField resignFirstResponder] (possibly added to the textFieldShouldReturn: UITextFieldDelegate method to support dismissing the on screen keyboard upon press of the return key).

I can confirm that adding e.g.

[textField performSelector:@selector(becomeFirstResponder) withObject:nil afterDelay:10];

to the TextFieldsViewController in WOCCatalog does result in the field gaining focus - but the onscreen keyboard does not automatically appear.

@ehren
Copy link
Contributor Author

ehren commented Jan 27, 2016

Just as a sanity check I compiled and ran the C++ touch keyboard sample app from
https://code.msdn.microsoft.com/windowsapps/Touch-keyboard-sample-43532fda
The touch keyboard does appear - so a fix for UITextField should be doable.

@ehren
Copy link
Contributor Author

ehren commented May 6, 2016

More or less fixed by #483 (or at least the touch keyboard appears!)

@ehren ehren closed this as completed May 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants