Design Team/Activity Touch Input: Difference between revisions

Garycmartin (talk | contribs)
Garycmartin (talk | contribs)
Line 114: Line 114:
* Default to large blocks when used on a touch device to reduce obscuring effect of fingers & improve hit target. Perhaps extend the block shapes to have an otherwise blank  'gripper/ridged' area to the left or right
* Default to large blocks when used on a touch device to reduce obscuring effect of fingers & improve hit target. Perhaps extend the block shapes to have an otherwise blank  'gripper/ridged' area to the left or right
:''What is the purpose of the gripper? --Walter'''
:''What is the purpose of the gripper? --Walter'''
::''To allow a fat finger to easily drag a block about without obscuring its content and top edge for snapping onto other blocks''
::''To allow a fat finger to easily drag a block about without obscuring its content and top edge for snapping onto other blocks --Gary''
:::''Got it. It could be something that only appears on a touch-enabled machine (or when the XO is in tablet mode). I'll sketch something up. --Walter''
:::''Got it. It could be something that only appears on a touch-enabled machine (or when the XO is in tablet mode). I'll sketch something up. --Walter''
* Portrait orientation clips too many toolbar icons (expect portrait orientation to be used much more frequently on tablet devices)
* Portrait orientation clips too many toolbar icons (expect portrait orientation to be used much more frequently on tablet devices)
Line 125: Line 125:
* Tapping a block tile or stack does not auto run it
* Tapping a block tile or stack does not auto run it
:''What is the difference between a tap and a click? (I added some code for XO3 to try to disambiguate between a tap and a small drag used in repositioning a block... may need revisiting) --Walter''
:''What is the difference between a tap and a click? (I added some code for XO3 to try to disambiguate between a tap and a small drag used in repositioning a block... may need revisiting) --Walter''
::Not sure from an implementation perspective, just an observation of the current behaviour in TA, I can click a block/stack to auto run, but a tap and release (many careful attempts) of the same block/stack had no effect.
::''Not sure from an implementation perspective, just an observation of the current behaviour in TA, I can click a block/stack to auto run, but a tap and release (many careful attempts) of the same block/stack had no effect. --Gary''


==Typing Turtle==
==Typing Turtle==