Linked by Thom Holwerda on Thu 26th Apr 2012 22:09 UTC
PDAs, Cellphones, Wireless As I already said yesterday - a bit colourful to get me point across - this older article of mine has proven not to be as accurate as I thought it was, in light of a heap of new information. I want to offer some more background to all this.
Thread beginning with comment 515860
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Android's pivot
by akrosdbay on Fri 27th Apr 2012 02:01 UTC in reply to "RE: Android's pivot"
Member since:

Apple TV runs iOS. iOS handles non-touch input just fine.

Reply Parent Score: 4

RE[3]: Android's pivot
by mrstep on Sat 28th Apr 2012 07:07 in reply to "RE[2]: Android's pivot"
mrstep Member since:

iOS - UIKit specifically - doesn't have event processing at the SDK level for mouse or key events, which makes perfect sense since it's designed for a touch interface - mouse movement/clicking and key handling isn't the same as multi-touch.

I'd encourage you to take a look at how the iCade SDK has to work around the missing key events to get joystick and button events into games that support it. (Start with a hidden text field's delegate and go a bit downhill from there since that delegate doesn't know about 'key down' or 'key up' either...)

Again, that in no way makes iOS less flexible since it's a UIKit design question, and having mouse events - or in 99.9% of the time keyboard events - in UIKit would needlessly complicate event handling, but it's a stretch to claim it handles all kinds of input equally well.

Reply Parent Score: 3