Talk:OLPC Human Interface Guidelines/The Sugar Interface/Input Systems: Difference between revisions
Jump to navigation
Jump to search
(Trackpad as Mouse - right button) |
|||
| Line 6: | Line 6: | ||
From what I understand, the clicking on the right mouse will bring up the contextual menu. Fine. But why from the '''element''' underneath? In the land of [[Smalltalk]] the contextual menu is relative to the '''selection''', not the position of the mouse. One annoying thing about some interfaces, is that the ''context-click'' is '''also''' a ''select-click'' making the interface counter-intuitive. |
From what I understand, the clicking on the right mouse will bring up the contextual menu. Fine. But why from the '''element''' underneath? In the land of [[Smalltalk]] the contextual menu is relative to the '''selection''', not the position of the mouse. One annoying thing about some interfaces, is that the ''context-click'' is '''also''' a ''select-click'' making the interface counter-intuitive. |
||
:Actually, I would argue the opposite on this point. One of the things we've tried hard to do is make things strongly contextual: information relevant to a particular object or control is accessed and displayed contextually, and positioned spatially on screen to support that. As such, clicking on an object (right-click or otherwise) should always have a reaction that's contextual to the element clicked upon. The idea that the previous selection is the target of any right-click, regardless of the cursor position when the click is made, supports a modal approach where there is first a selection action, followed by a "give me more info" action. - [[User:Eben|Eben]] 15:26, 20 February 2007 (EST) |
|||
If the objective is to place a way to ask things like 'what is this element', then it could be done when there's no selection (or is nil). --[[User:Xavi|Xavi]] 11:15, 20 February 2007 (EST) |
If the objective is to place a way to ask things like 'what is this element', then it could be done when there's no selection (or is nil). --[[User:Xavi|Xavi]] 11:15, 20 February 2007 (EST) |
||
:This is true inasmuch as the clicked upon element needn't be selected at all prior to clicking, which supports the "select-click" you mentioned above. - [[User:Eben|Eben]] 15:26, 20 February 2007 (EST) |
|||
Revision as of 20:26, 20 February 2007
Trackpad as mouse--Would it make more sense for the rightmost button below the trackpad to be the primary button? It is closer to the right hand, and most people are right handed. 24.19.6.204 16:44, 11 December 2006 (EST)
- When you think about it, in order to position the index finger centrally on the trackpad, the thumb of a right-handed individual will naturally rest either directly in the middle, or perhaps even moreso over the left mouse button than the right, especially due to the small size of the trackpads on the laptops. - Eben 13:10, 22 December 2006 (EST)
Trackpad as Mouse - right button
From what I understand, the clicking on the right mouse will bring up the contextual menu. Fine. But why from the element underneath? In the land of Smalltalk the contextual menu is relative to the selection, not the position of the mouse. One annoying thing about some interfaces, is that the context-click is also a select-click making the interface counter-intuitive.
- Actually, I would argue the opposite on this point. One of the things we've tried hard to do is make things strongly contextual: information relevant to a particular object or control is accessed and displayed contextually, and positioned spatially on screen to support that. As such, clicking on an object (right-click or otherwise) should always have a reaction that's contextual to the element clicked upon. The idea that the previous selection is the target of any right-click, regardless of the cursor position when the click is made, supports a modal approach where there is first a selection action, followed by a "give me more info" action. - Eben 15:26, 20 February 2007 (EST)
If the objective is to place a way to ask things like 'what is this element', then it could be done when there's no selection (or is nil). --Xavi 11:15, 20 February 2007 (EST)
- This is true inasmuch as the clicked upon element needn't be selected at all prior to clicking, which supports the "select-click" you mentioned above. - Eben 15:26, 20 February 2007 (EST)