Many thanks
On 3月25日, 下午12时56分, j <[EMAIL PROTECTED]> wrote:
> This GUI behavior is by design. See thread:
>
> http://groups.google.com/group/android-developers/browse_thread/threa...
>
> There are a few other threads on this topic.
>
> On Mar 24, 8:45 pm, babyblue <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > By the way, both of my laptop(XP) and PC(Vista) have this issue. I
> > thought M5 was designed in this way......Does anyone else have issue
> > to touch for a second time to make input valid when not in touch mode?
>
> > On 3月25日, 上午2时19分, Dave <[EMAIL PROTECTED]> wrote:
>
> > > Issue 502 has been denied since the Android Support Team could not
> > > reproduce it. However, this behavior did not occur in m3 and it does
> > > occur when I try it in on both Windows XP and Mac Leopard. So, if a
> > > few of you could try it and reply with your results, it would be
> > > greatly appreciated.
>
> > > If you enter the Dialer application and touch a few of the numbers and
> > > then wait more than 30 seconds, it will require two touch to enter
> > > another number. This ruins my interface since think time can be
> > > required. Imagine a chess game that requires you to prime the touch
> > > mechanism before you could move if you take more than 30 seconds.
>
> > > - Dave
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
Announcing the new M5 SDK!
http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
