microsoft / microsoft/WPF-Samples

TouchKBRegister causes form to act differently on keyboard show

Open
#249 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
5.7k
Forks
3.3k
Avg merge
12d 8h
Merged PRs (30d)
2

Description

I'm running on Windows 10 1909. Developing in Visual Studio 2017.

Standard operation, with a form maximized, bringing up the keyboard causes the form to be put into normal state with the form given the area above the keyboard.

But using TouchKeyboardEventManager, adding events for show and hide, now when then keyboard is shown the form stays maximized and the keyboard overlays the form.

I do understand that the example project needs the keyboard and form to act in this way, but I am desperate for show and hide events from the keyboard and the form to act like it does normally (i.e. form goes to normal state).

I can't see what might be causing this in the code. Is what I'm trying to do possible at all?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the example project and the TouchKeyboardEventManager show and hide event handling described in the issue. Compare the form behavior with and without those events on Windows 10 using Visual Studio 2017. Done means the events remain available while showing the keyboard causes a maximized form to return to its normal state instead of being overlaid.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.