3 ms·

Thanks. This story: http://news.ycombinator.com/item?id=1235081 http://news.ycombinator.com/item?id=1235081 talks a bit about the points you've made. Basical

by ximeng 17y ago

Thanks. This story: http://news.ycombinator.com/item?id=1235081 http://news.ycombinator.com/item?id=1235081 talks a bit about the points you've made. Basically you put a passive delay in that's long enough for people to cancel. It's not going to work for everything though - sometimes you really do want to start a process immediately. The biggest benefit comes when you've got a large bit of empty space on one side of an object. That space then becomes clickable. In a world with big monitors it's harder to get easy UI wins by putting important widgets on the side of the screen. You could get a similar effect with these bubble cursors.

nwinter 17y ago
I just tried limiting the max bubble cursor radius in your demo and it seemed to prevent the unwanted gap-clicking problem well enough, while still helping buttons be easier to click. Not sure if it reduces the win in the proposed huge-screen example.
- ximeng 17y ago
  On my local copy I put in something so that it looks at the second closest object to the cursor. Then only selects if the nearest object is 40% closer than the second nearest. It works pretty well to prevent ambiguity, but still gets a bit confusing when there's a few objects of different sizes nearby. Quite want to try this functionality in a real user-interface now!
jerf 17y ago
"Adding a passive delay" is very nearly a synonym for "adding latency". Not quiet. But close.