So far I have not found a solution for the button latency but I agree with Revar that it is possible to get about 2 button press onclick notifications per second.
I created an example that illustrates the problem and placed it <a href="http://www.creativecreek.com/latencytest.html";>here</a>. It is the simplest possible page I could create that illustrates the problem. The "button" is a styled anchor link with a solid background color and an onclick handler that just adds one to a number. The redraw and handler execution time should be minimal in this case. On the iPhone, I can tap the test button about 18 times in 10 seconds (1.8 taps/sec) without losing a tap. If I wait until the number changes before tapping again, then the fastest I've been able to go is about 15 taps in 10 seconds (1.5 taps/sec). I'd like to be able to receive notifications at the rate of 4 taps per second to get my calculator to "feel" responsive. I"m guessing that the problem is that mobile Safari is wailing until it is clear that the user has not double tapped before sending the onclick notification (onmousedown doesn't get delivered any faster). I would love to have some type of meta tag (with a possible associated custom notification) that would inform Mobile Safari that the initial tap should be delivered as soon as possible. - Clay On Oct 4, 3:34 pm, [EMAIL PROTECTED] wrote: > I found on my scicalc app that I could get about two buttonpresses > per second, if instead of using a <button> I used a <div> tag with > onclick= and an appropriate CSS styling to make it look nice. But > it's still slow. > > - Revar > > On Oct 2, 2007, at 11:23 AM, creativecreek wrote: > > > > > > > Does anyone know how to speed up button notifications? > > > I'm working on a calculator for the iPhone. I'm having a problem in > > that the button handlers (onclick handlers within an image map) are > > getting called after about a 1 second delay. The fastest I can tap > > numbers is about 1 per second. Faster than that and Safari recognizes > > a double tap instead. > > > It appears that Mobile Safari is waiting to see if a double tap occurs > > before sending the notification. Does anyone know of a way to > > disable double tap checking or another handler I could use that has > > less of a delay? > > - Revar --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en -~----------~----~----~----~------~----~------~--~---
