This posting is older than 6 months and can contain outdated information.
Hello Joshua,
thanks for your feedback.
Double clicks are a great concept, yet they are not suitable for
remotes I fear. At least, if you want to make it usable as a general
purpose device as Remote Buddy is doing.
The problem with double clicks is simple:
You have to wait if a second button press occurs before knowing
whether a button press is to be interpreted as a single press or a
double click. As a programmer, you'd usually make your app wait for
something between 0.5 and 1.0 seconds before considering a press/
release pair of events to be a single click. That would add 0.5 to
1.0 seconds time lag between a button press and any reaction. Also,
if you would like to quickly go back or forth a few tracks in i.e.
iTunes and repeatedly press a button, like, 5 times, what should the
app do with that? Is it two double clicks and a single click .. or
five single clicks?
So, adding support for double clicks - from my point of view - would
mean to risk reliability, ease of use, in-time responses and accurate
navigation using multiple clicks. All you'd get in return is - in
theory - a couple more mapping possibilities, which would probably
not be put to much use since single click, double click and hold
states are just too much to keep in mind at the same time for the
whole experience to be still intuitive and usable.
Sure enough you don't have this kind of problems with double clicks
with the mouse. If you click something once in the Finder, it can be
selected instantly. If you happen to click it again, the item it is
launched. But, and that's what makes all the difference, it was
possible to instantly react to the first click and not trigger an
unwanted action with that.
Best regards,
Felix
