<br><br><div><span class="gmail_quote">On 16/07/07, <b class="gmail_sendername">Jeremiah Flerchinger</b> <<a href="mailto:jeremiah.flerchinger@gmail.com">jeremiah.flerchinger@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Mohammed Musallam wrote:<br>> "many programs almost require a right-click."<br>><br>> That's based on the assumption you're using a desktop device (just<br>> what pauric said) and we must try to avoid that. I know I've been
<br>> running the same sentence over and over but look at the iphone (LATI) :)<br>><br>> well the idea behind taking away the right-click is to force the<br>> designers to better design their programs work flow.
<br>I see your point. Of course if we just call the events by different<br>names this argument goes away. Call them "simple press" and "extended<br>press" for example. In the contacts menu a simple-press could select a
<br>contact & bring up a page specific to that contact for calling, editing,<br>etc. A extended press could initiate a call and bring up a dialog to<br>cancel.<br><br>They're just events mapped to functions and we can call them whatever we
<br>like. One is a basic event and the other can be an advanced event. I<br>would say most apps use single clicks for simple/basic events and right<br>clicks for advanced events. Single-clicks and double-clicks are more
<br>common to desktops and filesystem browsing. The appropriate behavior<br>can be used in the appropriate instance.<br><br>Again I think we're just arguing over names, when event behavior is the<br>real issue.<br><br>
</blockquote></div><br>On the desktop where double-click is enabled, singe-click is mostly used to select things. On OpenMoko, you could also select things by tap&drag, and then drop the double-click.<br clear="all"><br>
-- <br>Vincent