Processing Ajax...

Title

Message

Confirm

Confirm

Confirm

Confirm

Are you sure you want to delete this item?

Confirm

Are you sure you want to delete this item?

Confirm

Are you sure?

User Image
Hans-Peter_in_DC
95 discussion posts
Re: Windows 10 1803>17134.191
Display Fusion 9.3

Would it possible to display the Tablet Keyboard icon [C:\Program Files\Common Files\microsoft shared\ink\TabTip.exe] on DF Taskbar 2 ONLY and then, when executed, have the keyboard panel display ONLY on that monitor?

Many thanks and good wishes to the DF Team,

Hans-Peter Guttmann
Jul 30, 2018  • #1
Keith Lammers (BFS)'s profile on WallpaperFusion.com
At the moment there's no public API for opening the touch keyboard, so it's not something we can add to the DisplayFusion taskbar :(

I've also tested in the past to try to get it to move to another monitor with Trigger rules, but it seems to ignore the move commands we send it.

What you could do is use the other on screen keyboard. You can create a shortcut to C:\Windows\system32\osk.exe. Trigger rules seem to work for it as well :)
Aug 1, 2018  • #2
User Image
Hans-Peter_in_DC
95 discussion posts
Keith, it's been a while … thank you very much for the prompt reply and researching my question.

Indeed, OSK. EXE works as you describe. But it does not access Emoji as the Touch Keyboard does directly. That was my purpose. Maybe in a new version of Windows 10, although it's a little hard to image Microsoft grasping the need to place that feature on a secondary monitor.

Meanwhile, my simple solution now is to place 'PopChar Win' on DF2 and set it to open to Segoe Emoji. Of course, 'Pop Char' — a superb utility — is so powerful it's nearly overkill.

As always, grateful for your help; all good wishes,

Hans-Peter
Aug 1, 2018 (modified Aug 1, 2018)  • #3
Keith Lammers (BFS)'s profile on WallpaperFusion.com
No worries! Thanks for letting me know about PopChar, that looks pretty handy!
Aug 1, 2018  • #4
User Image
Spa Malot79866
1 discussion post
I am very much curious if Microsoft has granted access to the Windows 11 On-Screen (Touch) Keyboard API 5+ years later? Seems a bit obsurd to gatekeep such a crucial accessibiliy tool, no? One would think that the solution would just to allow redundant instances with unique positions on the taskbar for each display, but I've also discovered that you cannot have multiple touchscreen inputs which is probably why they didn't bother... I'll keep checking github for a 3rd party hero to make my life slightly better, and will report any findings. ILI_I___H___I_LII
Jun 27, 2024  • #5
Subscribe to this discussion topic using RSS
Was this helpful?  Login to Vote(-)  Login to Vote(-)