R
Rob
[If this is in the wrong group, suggestions on a better one are
welcome...]
Windows XP's "on-screen keyboard" accessibility tool accepts clicks on
a virtual keyboard and sends them to whatever app has the input focus.
But it does one neat thing I can't reproduce: it does not appear to
steal the focus from the other active app when you click on its keys.
(It's in the "Accessibility" program group; try it for a better
explanation.)
I've written an onscreen keyboard as part of a touchscreen app I'm
writing, and it works great. But ... for the brief moment after the
user touches one of the keys, my virtual keyboard gets the focus before
sending it back to the other app. This results in a noticeable "blink"
or "wink" or "flash" of the other app's grabber, etc.
Anyone done this know how MS's on-screen keyboard accepts clicks on the
keys but doesn't appear to take the focus?
I've looked in the typical places (codeproject, guru, sourceforge,
google, etc.) to no avail. Thanks!
....R
welcome...]
Windows XP's "on-screen keyboard" accessibility tool accepts clicks on
a virtual keyboard and sends them to whatever app has the input focus.
But it does one neat thing I can't reproduce: it does not appear to
steal the focus from the other active app when you click on its keys.
(It's in the "Accessibility" program group; try it for a better
explanation.)
I've written an onscreen keyboard as part of a touchscreen app I'm
writing, and it works great. But ... for the brief moment after the
user touches one of the keys, my virtual keyboard gets the focus before
sending it back to the other app. This results in a noticeable "blink"
or "wink" or "flash" of the other app's grabber, etc.
Anyone done this know how MS's on-screen keyboard accepts clicks on the
keys but doesn't appear to take the focus?
I've looked in the typical places (codeproject, guru, sourceforge,
google, etc.) to no avail. Thanks!
....R