Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Enabling on-screen keyboard in simulator

How can I enable the on-screen, virtual keyboard in the BlackBerry 10 alpha simulator?

I'm having some troubles inputting text into my ported Android application, and had read that the PlayBook simulator also had problems with inputting text through the host PC's keyboard.

I've enabled "Keypress Pop-up" (not knowing what it does) in the "On-screen keyboard" setting in the simulator's settings, but it appears to have no effect: On-Screen Keyboard settings

Is there any way to get the on-screen keyboard to appear, so I can test using that?

like image 851
Paul Lammertsma Avatar asked Jan 15 '13 08:01

Paul Lammertsma


People also ask

Can not type in iOS simulator?

Before you start typing (when the on-screen keyboard shows up), press just the command key by itself and then release it. This should re-enable the keyboard in the simulator.

How do you show touches on iPhone simulator?

You can show touch indicators in the iOS simulator by opening Terminal and running defaults write com. apple. iphonesimulator ShowSingleTouches 1 . You can turn this setting off again by running defaults write com.

How do I open the Developer menu in Simulation?

You can access the developer menu by shaking your device or by selecting "Shake Gesture" inside the Hardware menu in the iOS Simulator. You can also use the ⌘D keyboard shortcut when your app is running in the iOS Simulator, or ⌘M when running in an Android emulator on macOS and Ctrl+M on Windows and Linux.


1 Answers

I discovered that the on-screen keyboard only appears when dragging in from the bottom-left corner.

Furthermore, I discovered that in portrait mode, the keyboard doesn't display correctly:

Simulator in portrait; keyboard doesn't appear correctly

To get the simulator in landscape mode, drag from the bottom-right corner; the keyboard then does appear correctly:

Simulator in landscape; keyboard appears correctly

Incidentally, this didn't resolve my woes with text input. Since it works so sporadically, I believe this is simply due to the simulator still being in alpha. In fact, at the moment, various keys map incorrectly, such as "3" mapping to "1" and "4" to "8", but most of them simply not at all. This may have to do with android:inputType="number".

like image 125
Paul Lammertsma Avatar answered Sep 30 '22 11:09

Paul Lammertsma