StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>As a tablet user I can answer a few of your questions.</p> <p>First:</p> <blockquote> <p>You cannot very easily keep a "keyboard focus" on a window when the stylus has to trail out of the focused window to push a key on the virtual keyboard.</p> </blockquote> <p>Most of the virtual keyboards I've used (The windows tablet input panel and one under ubuntu) allow the program they are typing in to keep "keyboard focus."</p> <blockquote> <p>What happens when a stylus "lift" occurs? A press?</p> </blockquote> <p>Under Windows, the pressure value drops, but outside of that, there is no event. (I don't know about linux.)</p> <blockquote> <p>What API calls can be used to detect this? Does it just translate into standard messages with flags/values set?</p> </blockquote> <p>As mentioned above, if you can get the pressure value, you can use that.</p> <blockquote> <p>Whats a good way to test/emulate this when your development pc is a desktop? Am I just flying blind here? (I only have periodic access to a tablet pc)</p> </blockquote> <p>When the stylus is placed down elsewhere, the global coordinates of the pointer change, so, you can emulate the sudden pointer move with anything that allows you to change the global pointer values. (The Robot class in Java makes this fairly easy.)</p> <blockquote> <p>What represents correct behavior or best practice for tablet stylus awareness?</p> </blockquote> <p>I'd recommend you read what Microsoft has to say, the MSDN website has a number of excellent articles. (<a href="http://msdn.microsoft.com/en-us/library/ms704849(VS.85).aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/ms704849(VS.85).aspx</a>) I'll point out that the size of the buttons on your applications makes a HUGE difference.</p> <p>Hope this was of help.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload