Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
1
Found in
4.6.0f1
Issue ID
646106
Regression
No
Mouse input doesn't call touchscreen keyboard
Mouse input doesn't call touchscreen keyboard
Selecting input field with physical mouse, which is connected to touchscreen device, touchscreen keyboard doesn't appear.
Selecting input field with touch, touchscreen keyboard appears.
Physical mouse should work the same as touch input.
Reproducible with 4.6.0RC1 on Windows Store Apps. Also, should be reproducible on Android.
Repro steps:
1. open project "UIrc1Project";
2. build to Win Store Apps platform;
3. try clicking with connected mouse on input fields in the first scene called "Controls";
Comments (2)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
yoonitee
Dec 18, 2014 12:08
I disagree.
The touchscreen keyboard should only appear
1) if you touch the input control
2) if you have no keyboard.
yoonitee
Dec 18, 2014 12:08
I disagree.
The touchscreen keyboard should only appear
1) if you touch the input control
2) if you have no keyboard.