<div dir="ltr">On Mon, Sep 29, 2008 at 3:32 PM, Minh Ha Duong <span dir="ltr"><<a href="mailto:haduong@centre-cired.fr">haduong@centre-cired.fr</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Le lundi 29 septembre 2008, <a href="mailto:community-request@lists.openmoko.org">community-request@lists.openmoko.org</a> a écrit :<br>
<div class="Ih2E3d">> I'm just sending this out there for anyone working on a/the dialer UI.<br>
> At the moment with the qtopia (ergo, 2008.*) dialer the same part of<br>
> the screen is used for "answer call" as "end call", and since the UI<br>
</div>> is laggy (see below), I naturally hit answer call a second time and as<br>
<div class="Ih2E3d">> a result hung up immediately. Probably should avoid this UI design<br>
> pitfall in future dialer (and other) interfaces.<br>
<br>
</div>I agree too. Do you think there is a ticket open already ?<br>
<br>
</blockquote></div>Apart from that, don't you think call management function threads should get the highest priority attached when invoked? That should help the response times.<br><br>On a side note, I think there is a real need to reconsider the UI of the phone altogether. Should we start a wiki page to get user inputs?<br>
</div>