CODEWITHSUNDEEP
windows-8microsoft-metro
pkumar0
pkumar0

Reputation: 2239

Show/Hide Keyboard programmatically on windows8

I am trying to show/hide keyboard on a Windows Metro app programmatically. I initially thought I could do it using a collapsed textbox and setting focus on it. But it seems like that has been disallowed in this link. The link also talks about the AutomationPeer and TextAutomationPeer to accomplish this. Is there a resource on how to use these ?

Thanks in advance PK

Upvotes: 9

Views: 17057

Answers (5)

Juan
Juan

Reputation: 1382

If you add a textbox and then select properties> under Miscellaneos there is a property named PreventKeyboardDisplayOnProgrammaticFocus, check that and set the focus of your text box like this:

 HiddenSearchBox.Focus(FocusState.Programmatic);

Upvotes: 0

Yang C
Yang C

Reputation: 536

There is an example with the custom AutomationPeer, which seems to be helpful for the question.

Good guide for creating the programmatic keyboard logic.

Holp it could be help

Upvotes: 0

Mayank
Mayank

Reputation: 8852

Here is little PowerShell script I use to achieve that. You can do the same in C# by getting the service and starting/stopping it depending on your needs.

$serv = get-ciminstance win32_service -filter "name = 'TabletInputService'"
# if started stop it
if( $serv.State.equals("Running") ){
    Stop-Service TabletInputService
}
# if not set to disabled, disable it
# else set to auto and start
if( !$serv.StartMode.equals("Disabled") ){
    Set-Service TabletInputService -StartupType Disabled
    "TabletInputService Disabled"
}
else {
    Set-Service TabletInputService -StartupType Auto
    Start-Service TabletInputService
    "TabletInputService Enabled and Started"
}

Upvotes: -2

SurenSaluka
SurenSaluka

Reputation: 1591

Just put a TextBox and hide it. Set the IsReadOnly = true and set the tab index of the TextBox to 0, so keyboard will focus on that TextBox but it realize TextBox is readonly and it will not poped up. :)

Upvotes: 1

N_A
N_A

Reputation: 19897

From here:

UI Automation is the mechanism through which developers communicate whether or not a particular UI element can receive text input. You must ensure that the appropriate accessibility properties are set in your apps so that the touch keyboard will know to appear when focus lands on a specific UI element. For Windows-provided controls, this will be done automatically because proper accessibility properties are set by default, but for custom controls and experiences you must do additional work to set the accessibility properties correctly; remember that the touch keyboard reacts to these properties.

If you use C# or C++, use an AutomationPeer object, and specifically a TextAutomationPeer. A Windows 8 Release Preview sample will demonstrate how to do this in C#. Remember that the control must also be editable and able to receive text to get the keyboard to invoke, in addition to having the appropriate accessibility settings. Indicating that something can receive text when it cannot will mislead accessibility tools and the users who rely on them.

To enable user-driven invocation, we track the coordinates of the last touch event and compare them to the location of the bounding rectangle of the element that currently has focus. If the point is contained within the bounding rectangle, the touch keyboard is invoked.

So you cannot programmatically show the keyboard. The appropriate way to hide/show the keyboard is by setting your control to accept input using an AutomationPeer object.

From here, if you set the input control to read-only then it will not trigger the keyboard, so possibly you could use that to control when the keyboard opens.

Edit:

There are a few things to check when implementing the text automation peer:

  1. Make sure you either test with a real touch device or test using the simulator with the Basic Touch Mode tool. If you don't do this the automation peer won't activate since it is only activated by a stylus or a touch input (not mouse).

  2. Make sure your custom control implements OnCreateAutomationPeer something like this:

    protected override AutomationPeer OnCreateAutomationPeer() { return new CustomControl2AutomationPeer(this); }

  3. Make sure your Automation Peer implements FrameworkElementAutomationPeer, ITextProvider and IValueProvider

More details found in the example here.

Upvotes: 3

Related Questions