Now *that* is exactly what I needed. Should be required reading.
Why didn't runrev hire this guy to write more of their manuals in this
style?
Thanks muchly!
-Ken
On 29/01/2012 19:51, stephen barncard wrote:
you should check out Dar Scott's primers on Message Mechanics.
Visually and techni
you should check out Dar Scott's primers on Message Mechanics.
Visually and technically informative.
http://pages.swcp.com/dsc/revstacks.html
On 29 January 2012 11:38, Ken Corey wrote:
> Here's the basic idea of the code I needed.
>
> the touchMove event arrives in no particular order, and in
Here's the basic idea of the code I needed.
the touchMove event arrives in no particular order, and in no particular
time.
If you absolutely have to have a timeout, you can't just test for a
timestamp on the next run of touchMove, because there might not be
another touchMove.
I'm not quite
You might try:
wait 30 millisecs with messages
Regards,
Scott Rossi
Creative Director
Tactile Media, UX Design
Recently, Ken Corey wrote:
> I've been working on a pinch library for a week or so, and I have
> complained about the jerkiness. I am thinking that the problem is that
> it's /too
I've been working on a pinch library for a week or so, and I have
complained about the jerkiness. I am thinking that the problem is that
it's /too/ repsonsive.
The instant one touch moves, it's causing the pinchMove event to be
generated. This is fine if nothing else truly has moved, but if t