I am creating a WPF application that will be used both on the desktop and on the Surface Pro tablet, which contains an update for Win10 developers.
If the text field receives focus, the Win10 screen panel should open at the bottom of the screen and move the application up the screen to click on the focused element again.
I implemented WpfTabTib , which worked very well until we updated the tablet to the creators version. Technically, it still works, but with ugly animations moving the window up, down, and up to open the keyboard.
After reading that microsoft configured the keyboard behavior according to uwp behavior, I updated my .Net infrastructure to 4.6.2 without the expected result. Microsoft doesn't seem to care about that.
Does anyone have the same problem or a different approach for me?
Thank you so much!
Edit: updating the tablet to the insider preview of the upcoming Windows Fall update changed behavior again: the opening animation is now a little better, but still far from pleasant. And since the new problem closing osk does not put the application back.
source
share