You're right, the TIP isn't customizable because it's system wide but the PIP allows some customization like factoids and which panel is visible; is your motivation limited to an app or is it system wide?
To partially answer your original question, the TIP and PIP use either TSF or SendInput, depending on the control. For example, only the Win32 RichEdit control v4.1 or later handles TSF and surprisingly the winforms RichTextBox control doesn't wrap this version so you'd have to use SendInput for that one. Ironically the managed InkEdit control does wrap the later version and as you know, it uses TSF. -----Original Message----- From: Larry O'Brien [mailto:[EMAIL PROTECTED] Sent: Monday, June 23, 2003 9:53 PM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Virtual keyboard strategy - TFS or SendInput? If the TIP allows for user-customization, can you point me towards documentation? > -----Original Message----- > From: Kollen Glynn [mailto:[EMAIL PROTECTED] > Sent: Monday, June 23, 2003 12:14 PM > Subject: Re: Virtual keyboard strategy - TFS or SendInput? > > Larry, > > I'm curious, are you not getting some functionality from the TIP or > PIP? > > -----Original Message----- > From: Larry O'Brien [mailto:[EMAIL PROTECTED] > Sent: Monday, June 23, 2003 11:28 AM > To: [EMAIL PROTECTED] > Subject: [ADVANCED-DOTNET] Virtual keyboard strategy - TFS or > SendInput? > > > I'm thinking of putting together a virtual keyboard for the Tablet PC > (choice between QWERTY, ATOMIK, and user-customizable layouts [like a > programmer's keyboard with '[EMAIL PROTECTED]&*()' etc. as non-shifted chars]). > It would seem that the "most proper" way to do this would be to use > Text Framework Services, but as yet TSF seems to be > under-documented (there's > one short example in the Platform SDK and, as far as I can > see, nothing > else). The other option would be to use SendInput while > somehow writing > an app that either never gets focus or continually resets it to the > targetted window. > > So, to do it in managed code, I seem to have a choice: relatively easy > WinForms & complex interop or complex WinForms & easier interop. My > bias says "WinForms is well designed and close to the undrlying OS, so > 'subverting' activation should be relatively straightforward." On the > other hand, interop is so important that I feel I'm 'doing wrong' by > shying away from it. Thoughts? > > And while I'm asking -- anyone have any TFS examples? :-) > > Cheers, > Larry > http://www.ThinkingIn.NET/ >
