On 05/02/2011 08:06 AM, Robin Burchell wrote: > (The M::OrientationAngle enum has been copied. I think a nicer > solution would be for it to use QOrientationReading's enum, but > that's probably for the future.)
Yeah, that would be an API change to MInputContext, which wasn't an option at the time. This is really the only spot where stuff in the MTF namespace appears in the public face of MInputContext. Unfortunately that representation (the enumerant values are just rotation angles in degrees, by the way) is part of the keyboard's IPC protocol, so even fixing it in the API won't elimianate it. The VKB was written to MTF originally, after all. But I agree that forcing the app to manage the keyboard rotation in the default case is kind of wrong. Clearly the right choice is that the keyboard rotates on its own with the device, and apps (landscape-only games, etc...) that need to override that behavior would use the special hooks. Andy _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
