This eventually (sorry) gets around to a question about Dolphin. I'd
appreciate any insights you might have:
The long-awaited new pen tablets finally arrived today! Initially, I was
quite concerned that they would be disappointing (to say the least) to their
users because the often-used on-screen keyboard is almost uncontrollable.
The buttons often "stick" and end up entering several characters when one
was intended to be typed (kinda sounds like votes in Florida now that I
think about it). Strictly speaking, the machines are defective out of the
box, but, that's (of course) one for the reseller.
As I've played around with one of the machines, it's become "obvious" that
push buttons act badly when the user clicks and releases at the same point.
"Dragging across" a button will often give an immediate response, where a
click/release w/o movement will typically leave the button depressed for
considerably more than the magic 0.1 seconds that causes users to notice
that nothing happened. There is a chance that this is the root cause of the
problem with the on-screen keyboard, and I've noticed it in several apps
now, in addition to one deployed Dolphin app.
What does this have to do with Dolphin menus? Well, I've noticed similar
behavior in the Dolphin app's context menus. Can you think of any possible
connection, other than maybe something wrong in the machine's implementation
of the DefaultWindowProc?
BTW, aside from intermittent disinterest in the release of pushbuttons
(which is happening machine-wide), the Dolphin app performs very well. I
should also mention that the problems were evident before any OA or UF
software was installed. If the problems can be resolved, these machines
will serve nicely.