Edge.Point

1. Nathan – Peter - Kaitlyn Edge.Point

2. Initial Design Sketches

3. Started with Crossing • Cross over, cross back, etc • Gestures • Acceleration/Velocity based Select

4. Wright Cursor

5. Wright Cursor

6. Wright Cursor

7. Wright Cursor

8. Wright Cursor

9. Wright Cursor

10. Wright Cursor

11. Wright Cursor

12. Wright Cursor

13. Wright Cursor

14. Wright Cursor

15. Wright Cursor

16. Pure crossing seems to be: • Error-prone • Unusable in current interfaces • Unsafe

17. So we went to : EDGES!

18. Edges: • Very accurate • Still Crossing, just like Mac Menubar • Pretty Safe Ah Ha! – Make everything as easy to click as the buttons on a screen edge!

19. Flipbooks: Hash out our Ideas We also tried a binary search, quadrant area cursor. 1 2 5 6 While it has potential, we think edges are too powerful to pass up. 3 4

20. An area cursor follows the mouse, separating the selection area into 4 quadrants. 4 1 5 2 3 6

21. Activation causes the cursor to move independently of the area cursor. 4 1 5 2 3 6

22. Moving to the edge of a quadrant modifies the selection to contain only the items from that quadrant. The edge constrains the mouse and keeps it in the area cursor. 4 1 5 2 3 6

23. The items from the selected quadrant are rearranged into quadrants. Now, going into a quadrant selects the remaining items. If more than one item is in the quadrant, the process is repeated. 1 2 5 6 3 4

24. 1 2 5 6 3 4

25. 2 6

26. Selecting a quadrant with only one remaining target selects the target. 2

27. Activate tunnels • Keystroke • Click Target

28. What if the mouse is over a pliant region? … that ISN’T your target? Target

29. What if the mouse is over a pliant region? … that IS your target? Target

30. What about right-clicking? Open Copy Target Properties

31. Edge.Point

32. Interaction Time!

33. Pros: Plausible! • Does not hamper user who do not need or want pointing assistance. • Works with current desktop interfaces. • Effective widths of targets = ∞ • Steering tasks are automated by tunnels. • Resize area cursor via mouse-wheel.

34. Cons: • Must deploy area cursor to gain assistive benefit. • Mouse buttons are used. • Algorithms could be improved to better map tunnels to the cursor.

35. User Tests

36. Without explanation or practice, the technique was very hard to use for our subjects. They ended up just pointing and clicking the icons. Normal interaction still works perfectly, a feature of our system.