[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: xAP switch
- Subject: Re: xAP switch
- From: Patrick Lidstone
- Date: Fri, 18 Apr 2003 11:57:00 +0000
--- In <a
href="/group/xAP_developer/post?postID=095RlieuknjFt-XDt1ZmcskXnWf4BQd7qANjoB_175v-y-Tq88Qfu4wrkTEaq2rz1HGMR3AkRmn8SKJiBG0VZ0WhswISpQ">xAP_developer@xxxxxxx</a>,
"Paul Gordon"
<paul_gordon@h...> wrote:
> Hi Kev,
>
> Yeah, I appreciate the need to differentiate, I was just curious as
to why
> its necessary to use any more than two events or two states to do
so...
> Think of the way a PC keyboard operates, - there is a key down
event
> generated when a key is pressed, and a key up event generated when
it's
> released.. - the time duration between these two events is how long
it's
> held down for, - thus enabling a short press or a long press to be
> deduced...
>
> Not that it matters though, I was just curious on a purely
intellectual
> level... :-)
>
I think it's probably just a design tradeoff. It's easier/cheaper to
detect a long vs short push at source than to insist all receiving
devices have built-in timer/intelligence to decode the third state.
Patrick
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|