Keypad layout app password#
Keypad layout app windows#

The effect of the input scope on the features enabled by the IsSpellCheckEnabled and IsTextPredictionEnabled properties is listed for each input scope.

Keypad layout app windows#

These tables show the Windows Soft Input Panel (SIP) layouts for common input scope values. Instead, the keyboard is shown only when the user interacts with the control. PreventKeyboardDisplayOnProgrammaticFocus-When this property is true, it prevents the system from showing the SIP when focus is programmatically set on a text control. For more info, see the tables later in this topic. Text prediction might be disabled if the input scope is other than Default, even if the IsTextPredictionEnabled property is true. You can select from the list so you don't have to type the whole word. IsTextPredictionEnabled-When text prediction is enabled for a text control, the system shows a list of words that you might be beginning to type. These auto-correction features might be disabled in other input scopes. Spell checking is enabled by default.įor the Default input scope, this property also enables automatic capitalization of the first word in a sentence and auto-correction of words as you type. You can tap a word to see a list of suggested corrections. IsSpellCheckEnabled-When spell check is enabled for a text control, the control interacts with the system's spell-check engine to mark words that are not recognized. To provide the best experience for your users, it's important to understand how these properties affect text input using touch.

The TextBox and RichEditBox controls have several properties that influence the behavior of the SIP. Text prediction, spell checking, and auto-correction phoneNumberTextBox.InputScope = new InputScope() The same steps can be condensed into this shorthand code. ScopeName.NameValue = InputScopeNameValue.TelephoneNumber InputScopeName scopeName = new InputScopeName() Set the InputScope object as the value of the text control's InputScope property. scopeName.NameValue = InputScopeNameValue.TelephoneNumber Īdd the InputScopeName object to the Names collection of the InputScope object. Set the NameValue property of the InputScopeName object to a value of the InputScopeNameValue enumeration. If it's not set, set the x:Name attribute so you can reference the control in your code. In the XAML file for your page, locate the tag for the text control that you want to change. With the InputScope set, a touch keyboard with a suitable layout for the data shows for each text box. Here are some text boxes that might appear on a common customer-contact form. In the XAML file for your page, locate the tag for the text control that you want to change.Īdd the InputScope attribute to the tag and specify the InputScopeNameValue value that matches the expected input. Here, you change the input scope of several text boxes to match the expected data for each text box.

Keypad layout app password#

The InputScope property on PasswordBox supports only the Password and NumericPin values.

This tells the system to show the number keypad layout, which makes it easier for the user to enter the PIN. The input scope provides a hint to the system about the type of text input expected by the control so the system can provide a specialized touch keyboard layout for the input type.įor example, if a text box is used only to enter a 4-digit PIN, set the InputScope property to Number. You can make it much faster and easier for users to enter data in your app by setting the input scope of the text control to match the kind of data you expect the user to enter. The touch keyboard is invoked when the user taps on an editable input field, such as a TextBox or RichEditBox. The touch keyboard can be used for text entry when your app runs on a device with a touch screen. To help users to enter data using the touch keyboard, or Soft Input Panel (SIP), you can set the input scope of the text control to match the kind of data the user is expected to enter.