4 ms·
A couple of things that aren't clear: firstly, does the manufacturer have to commit to certain button combinations at manufacture time, or is it runtime-configu
by apendleton 13y ago
A couple of things that aren't clear: firstly, does the manufacturer have to commit to certain button combinations at manufacture time, or is it runtime-configurable (in other words, can a user install a different keyboard with different button locations and still use it)? Second, is the user still triggering the keypress event just by touching, or is it actual depression of the button that does it?
- mgkimsal 13y agono idea but... i could see another type of event being needed - keyTouch and keyPress ???
- tobr 13y agoTouch in this case is rather like hover though. Lack of hover is one of the trickiest things in designing for touch screens right now. There's no good way to tell the user a bit more about what's going to happen, until they commit to a touch.
- nickloewen 13y agoI think the answer to the first question lies here: > Currently, the technology is limited in that it's a fixed single array. You wouldn't be able to use the Tactus keyboard in both portrait and landscape mode, for example. But the goal is to make the third generation of the product dynamic. "The vision that we had was not just to have a keyboard or a button technology, but really to make a fully dynamic surface," says cofounder Micah Yairi, "So you can envision the entire surface being able to raise and lower depending on what the application is that's driving it." Meaning it could display a keyboard when you're typing an e-mail, a number pad when you're dialing a phone number, and perhaps letter tiles when you're playing Words With Friends.