MCPE-57264The On-Screen Keyboard cannot be used with Windows 10 edition, as opposed to Java
Following up on a bug report I made on JE's tracker, JE issue #160175, I felt it was important to make you aware that, due to a lack of compatibility with the Windows On-Screen Keyboard, I'm unable to play Bedrock Edition, just as with the other issue I reported. Here's what I know so far:
first off, cards on the table, I don't know if there ever actually was compatibility between the OSK and BE; I just know that, much like when I tried to play Java edition 1.14 for the first time, I wasn't able to, and the symptoms are the same here. Specifically, if I place the on-screen keyboard over the app's window like I'm used to doing in Java Edition, bedrock ignores it and doesn't let me click anything on the keyboard, instead resetting the cursor's position regardless of where it is. I realize it may be a lot to ask for this "bug" (which only really qualifies as such because it's a game breaking discrepancy between editions) to be "fixed", especially given that what was actually going on in the case of Java was technically Undefined Behavior with LWJGL (which isn't even present in the case of bedrock), but nonetheless it's kind of a serious thing to not be able to play at all, you know?
Please let me know what other information you need from me, and if there's anything else I can do to help move this along.
(screenshot description: a picture of what my screen usually looks like when I play on Java Edition. Note the on-screen keyboard and the little blurb from Dragon NaturallySpeaking telling me what the last recognized voice command was. Normally, to move around or otherwise use keyboard controls, I would just click the virtual key I want, but that requires the cursor staying in one place over the on-screen keyboard)
- Incomplete
Twisted Code- 1
- 1
- Unconfirmed
- Windows
- Windows 10 version 1903 (OS Build 18362.476)
- accessibility compatibility input interface
- 1.14.0.50 Beta 1.13.2 1.13.1 1.13.0
Created Issue:
The On-Screen Keyboard cannot be used with Windows 10 edition, as opposed to Java
Following up on a bug report I made on JE's tracker, #160175, I felt it was important to make you aware that, due to a lack of compatibility with the Windows On-Screen Keyboard, I'm unable to play Bedrock Edition, just as with the other issue I reported. Here's what I know so far:
first off, cards on the table, I don't know if there ever actually was compatibility between the OSK and BE; I just know that, much like when I tried to play Java edition 1.14 for the first time, I wasn't able to, and the symptoms are the same here. Specifically, if I place the on-screen keyboard over the app's window like I'm used to doing in Java Edition, bedrock ignores it and doesn't let me click anything on the keyboard, instead resetting the cursor's position regardless of where it is. I realize it may be a lot to ask for this "bug" (which only really qualifies as such because it's a game breaking discrepancy between editions) to be "fixed", especially given that what was actually going on in the case of Java was technically Undefined Behavior with LWJGL (which isn't even present in the case of bedrock), but nonetheless it's kind of a serious thing to not be able to play at all, you know?
Please let me know what other information you need from me, and if there's anything else I can do to help move this along.(screenshot description: a picture of what my screen usually looks like when I play on Java Edition. Note the on-screen keyboard and the little blurb from Dragon NaturallySpeaking telling me what the last recognized voice command was. Normally, to move around or otherwise use keyboard controls, I would just click the virtual key I want, but that requires the cursor staying in one place over the on-screen keyboard)
Attachments1
- Unresolved
- Open
- Unconfirmed
- Windows
- Windows 10 version 1903 (OS Build 18362.476)
- 1.14.0.50 Beta 1.13.2 1.13.1 1.13.0
Following up on a bug report I made on JE's tracker, JE issue #160175, I felt it was important to make you aware that, due to a lack of compatibility with the Windows On-Screen Keyboard, I'm unable to play Bedrock Edition, just as with the other issue I reported. Here's what I know so far:
first off, cards on the table, I don't know if there ever actually was compatibility between the OSK and BE; I just know that, much like when I tried to play Java edition 1.14 for the first time, I wasn't able to, and the symptoms are the same here. Specifically, if I place the on-screen keyboard over the app's window like I'm used to doing in Java Edition, bedrock ignores it and doesn't let me click anything on the keyboard, instead resetting the cursor's position regardless of where it is. I realize it may be a lot to ask for this "bug" (which only really qualifies as such because it's a game breaking discrepancy between editions) to be "fixed", especially given that what was actually going on in the case of Java was technically Undefined Behavior with LWJGL (which isn't even present in the case of bedrock), but nonetheless it's kind of a serious thing to not be able to play at all, you know?
Please let me know what other information you need from me, and if there's anything else I can do to help move this along.(screenshot description: a picture of what my screen usually looks like when I play on Java Edition. Note the on-screen keyboard and the little blurb from Dragon NaturallySpeaking telling me what the last recognized voice command was. Normally, to move around or otherwise use keyboard controls, I would just click the virtual key I want, but that requires the cursor staying in one place over the on-screen keyboard)
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
why you want to use OSK when you have the PC keyboard?
ok, gif/video/ or screenshot when the cursor is locked.
enable OSK title bar, then click on "title bar" to activate the OSK.
if your OSK doesn't have this option download another VirtualKeyboard with title bar option.
moving mouse over OSK doesn't make the current working window to lose focus, maybe the "title bar" can.
Never mind, Now I understand, I've read MC-160715.
This can be done only by DLL injection.
#find somebody that is good at C/C++ programming.
![[Mod] OcelotOnesie](../../../data/avatars/users/43220.png){kind=small}
,
Concerning DLL injection: I am aware. I think you missed my point again. But even if you had gotten it, the point was kind of off-topic anyway. Perhaps we should strike these last three comments as well (this one, my previous one, and your reply to it), since we don't seem to be adding anything meaningful to the ticket.
(replying to AM's seemingly-now-deleted comment about this only been possible with DLL injection... which roughly translates to "the developers have to do it")
...which is why I'm reporting it as a bug rather than asking "how do I do this" because I feel it's the game's developers' responsibilities to make it accessible (within reason). JE is accessible to me but my friends like playing on BE. although I believe the former case might've been accidental, I don't think it would kill them to at least take a look at it to see what they can do. Had I paid for BE rather than receiving a complementary copy because I already owned JE when they released BE, something like this would make me immediately (if reluctantly) request a refund (which is another reason I am putting it here rather than on the overworked feedback tracker: missing but unavoidably necessary functionality is essentially a bug unless it was, and of course this is incredibly unlikely, the developers' intent to completely alienate someone).
![[MCQA] v-magwar](../../../data/avatars/users/18935.svg){kind=small}
Thank you for your report!
However, this issue has been temporarily resolved as Awaiting Response
Is this still an issue in the latest version?
If it is, please be sure to include steps to reproduce the problem:
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
as far as I know this is still a valid issue. Sorry I didn't reply sooner. I kind of dropped the ball
Steps to Reproduce:
1. load up Bedrock Edition on Windows 10
2. open up the Windows On-Screen Keyboard (C:\Windows\system32\osk.exe on, presumably, all versions of Windows 10. Certainly all that I am aware of but that's not saying much suppose. If that's not the executable name, try getting to it from the Ease of Access Center or mouse/keyboard settings)
3. Load any world and attempt to use the on-screen keyboard in place of your keyboard
Observed Results:
it is impossible to interact with the on-screen keyboard like I can do (at least when I disable raw mouse input) in JE because, as you should be able to observe, the cursor lock prevents the cursor from interacting with the on-screen keyboard no matter how fast you move the cursor
Expected Results:
By contrast, on JE, if I move the cursor fast enough so that it gets to the on-screen keyboard before it's pulled back, it will stay there until I move it off again. This is relatively workable behavior, and is about equal in usefulness as it would be if the cursor's actual position was not modified until it reached the edges of the game window as another voxel builder, Trove, does.
Wait, title bar? What does that have to do with anything? Are you talking about activating the OSK window when it is over the game? Because that would be impossible, regardless of title bar, for the same reason I specified above: I cannot get the mouse to go over to the on-screen keyboard because the cursor is locked when it's on the player's aiming reticle.
I will try what you said tomorrow, as the built-in OSK has a title bar by default, but I highly doubt it will help with the issue I described.
except that's not what I want to do. The OSK requires the working window to be in focus (otherwise it doesn't know where to send the keystrokes), and I don't want to change focus to the OSK or any other window. What I want is to be able to interact with the OSK AT ALL when the game is in focus and I don't have an inventory or any other menu open, but again, I cannot do so because I can only click things in the game world due to the cursor lock. That is to say, the issue isn't that I can't break out of the cursorlock to change focus; the issue is that if I do anything to change focus, it defeats the purpose of having put focus on the game window in the first place.
I'm guessing you either didn't try following my reproduction steps, or (despite my best efforts) didn't understand them, if you don't know what I mean. I'll see if I can get a GIF or video together later to demonstrate, since that's generally better than reproduction steps anyway...
Yes, please attach any video or a gif of this happening, I kind of get what you mean in the report but because it is a bug tracker, we need to have the best documentation possible that the issue occurs as you describe, which would be visuals.
If, of course, the issue still occurs.
Same problem here. When opening Minecraft windows edition, the on-screen keyboard of the accessibility tools is not usable anymore.
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
For any account or purchasing related issues, please contact Minecraft Customer Support directly, as we cannot assist with those here at the bug tracker.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki