Slashdot Log In
Making Fingers Work With Touch Screens
Posted by
kdawson
on Thu May 17, 2007 10:44 AM
from the seeing-the-spot dept.
from the seeing-the-spot dept.
An anonymous reader writes "A paper was recently published about Shift at the Computer Human Interaction Conference earlier this month. The authors (Daniel Vogel, a Ph.D. candidate at the University of Toronto and Patrick Baudisch, a research scientist at Microsoft Research) developed the technology to solve several problems with mobile-phone touch screens. Most such screens are designed to be operated with a stylus; when touched with a finger the UI doesn't work so well. They also created a short video with a demonstration of how Shift works. Shift builds on an existing technology known as Offset Cursor, which displays a cursor just above the spot a user touches on the screen. That allows a user to place their finger below the item they wish to choose so that they can see the item, rather than hiding it with their finger."
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
Just Hire A Manicurist... (Score:2, Insightful)
Re: (Score:3, Interesting)
FingLonger (Score:4, Funny)
Re: (Score:3, Insightful)
Counterintuitive (Score:5, Insightful)
Re: (Score:3, Interesting)
Re: (Score:3, Informative)
FTFS:
Am I the only one who read this and thought -- with a sigh -- that there was surely already an odious patent application filed for it?
"Method and Apparatus for Displaying a Cursor Below the Designated Location" -- with th
Re:Counterintuitive (Score:4, Informative)
Now if only they could solve the problem of screens getting smudged by fingers.
Parent
Re: (Score:3, Informative)
Re: (Score:3, Insightful)
Thats not counter-intuitive, thats exactly how basically *every* GUI today works. When you press a button the action takes place not on mouse-button-down event, but on mouse-button-up. Shift uses the time in between down and up to present the user with a little zoomed view of what is under his finger so that he can fine tune his selection. Looks pretty intuitive and easy to understand for
Re: (Score:3, Informative)
Oblig. Simpsons (Score:5, Funny)
Makes me wonder about the iPhone (Score:3, Interesting)
Re: (Score:3, Informative)
I know because I created the first such system.
Re: (Score:3, Informative)
Building touchscreen systems was not easy or cheap in those days. Today we don't even need computers to put touchscreens in front of users - just a display with a wireless network connection.
offsets? (Score:2)
That's intuitive (Score:5, Funny)
Just like when I use a telephone, I hit the buttons next to the number I am looking to dial and when I park my car, I park next to the spot I want.
Fingernails to the rescue! (Score:2, Interesting)
Users can change too (Score:2)
1. Use my fingernails. No fancy glue on stylus or anything, but finger nails don't leave oily traces unless I've just finished gutting a whale by hand or something.
2. I do it palm facing towards me, pointed up. This keeps the contact area visible the whole time. If the computer were british, it might look like I was flipping it off, sure, but it works well.
When you have limi
Not how it works (Score:4, Informative)
It'll throw me off (Score:4, Insightful)
Not that we can't learn. Just as spear fishers learned to take into account the refractive index of water when fishing. I'm sure it took a while, but after the learning period I'm sure it's second nature to aim X below what I want to kill.
I'm interested in seeing how Apple solved this problem with the iPhone
Re:It'll throw me off (Score:5, Funny)
It's amazing how much simpler everything is with only one button...
Parent
or you could... (Score:3, Interesting)
GUI / Hardware design (Score:5, Interesting)
The touchscreen for many devices is physically designed for use with a stylus. They require quite a bit of force to register, and it is difficult to apply that much pressure with a finger because of the amount of surface area contacted. The DELL Axim touchscreens work particularly well with finger touch, while others, like the Asus a716, do not.
GUI Design is critical. Microsoft's history with mobile devices has been to make them as much like Windows 95 (and up) as possible. Windows CE 1.0 was exactly like Windows 95. Although with Pocket PC (CE 3.0) they tried to follow Palm's dominant (at that time) lead, and simplify the GUI, it is still most conducive to mouse / stylus input. The iPhone is a perfect example of how to design a GUI for finger based input. The multi-touch hardware capability is not even an issue at this point - pure software design is responsible for the bulk of the usability.
Along those lines, Microsoft prefers static dialogs that show as much information at once as possible, requiring small, desktop-like controls that demand precision stylus input. The iPhone is dynamic, scrolling in new options as the user make selections. Thus they have room for large, finger-sized buttons, because the display changes constantly. Many controls, like scrollbars, are unnecessary because entire display areas (like lists) can simply be dragged and tossed, which is the most natural behavior in the first place. The scrollbar then becomes only a visual indicator, which can even be hidden when the user is not interacting with the screen.
I've put together some code that behaves like the iPhone's drag interface, both in 2D for rectangular regions, and 1D for lists. It works really well on the Axim, again, because its touchscreen is nice and sensitive, even when retrofitted to existing Windows List controls. So it obviously is not a matter of hardware, but GUI design, that Windows Mobile isn't conducive to touch input.
So basically, this article is not stating the real problem, which is that MS is completely missing the mark with the fundamentals of their mobile GUI. But instead it offers a clumsy hack to work around an improperly designed UI. The ironic thing is Shift's Offset Cursor doesn't work at the bottom of the screen. That area is the most important for user interaction, because controls are strategically placed their so the user's fingers (hand / stylus) conceal as little extraneous area of the display as possible. That is why onscreen keyboards are always at the bottom, which makes them inaccessible to this Shift hack. The article fails to mention that little detail too.
Dan East
This is sad. (Score:4, Insightful)
I had many conversations over the years dealing with this specific issue, of using the magnifying glass effect on the GUI to display the area occluded by the finger. I didn't implement this effect because I have not been doing much work on displays with a diagonal measurement of 2 to 3 inches, but it is an effect that was often the subject of conversations I've had with many people and even in some lectures I've given.
I'm sad to see that somebody has now decided to patent something that has been a common topic of touchscreen GUI conversations for many years. The patent can hardly be considered non-obvious. It could well be that the two people involved here, one a student, one a microsoft employee, are simply ignorant of the basic design issues of graphical touchscreen GUI's.
I would go so far as to say that this patent application is morally reprehensible, right up there in league with patents on seeds that have been around since the dawn of time.