Look in source code \ Reflector. There are lots of quirks in controls text processing, I doubt that any one will care to document this. For instance KeyDown event of TextBox is not fired when user presses BackSpace when there is text inside control, but fires when the is no text, etc. The quickest way … Read more
My version of Kinesis Advantage layout: For mac you can create custom layout (see TN2056), swap “Caps lock” to “Num pad” (and create layout for “Caps lock”) and use Keyboard Maestro (for copy/paste/redo/undo and text navigation). I can put it all to public if needed. For windows you can use AutoHotKey.
If neither enableSuggestions nor autocorrect can solve the problem, try setting keyboardType to TextInputType.visiblePassword.
We did it with this myLayout.getViewTreeObserver().addOnGlobalLayoutListener(new ViewTreeObserver.OnGlobalLayoutListener() { @Override public void onGlobalLayout() { Rect r = new Rect(); parent.getWindowVisibleDisplayFrame(r); int screenHeight = parent.getRootView().getHeight(); int heightDifference = screenHeight – (r.bottom – r.top); Log.d(“Keyboard Size”, “Size: ” + heightDifference); } }); We only resize views with the keyboard, so we could use this.
In your AndroidManifest.xml: <activity android:name=”com.your.package.ActivityName” android:windowSoftInputMode=”stateHidden” /> More details about windowSoftInputMode can be found here. This setting will hide soft keyboard when user enters new Activity (even if EditText control gains the focus). Soft keyboard will be shown only when user clicks the edit box control.
I think the best approach would be to combine HTML5 form attributes with an optional virtual keyboard link. HTML5 form attributes can be used to trigger different types of keyboards. For example, <input type=”email”>, <input type=”number”> and <input type=”tel”> will trigger the appropriate keyboard types on iOS (not sure about Android/WinPho/other, but I would imagine … Read more
I’m not really sure if there’s a straight-forward solution to this (to that extent that it is even possible to understand the real reason behind the original question). As is quoted in the original question: If you need some app-specific input, you should build it into your UI rather than pushing it out to a … Read more
You can do something easier. Add this to the LinearLayout (or any other layout that is the root): <LinearLayout … android:focusable=”true” android:focusableInTouchMode=”true” … />