I'm not sure what the motivation was to deprecate Display#getOrientation() in SDK 8 is, since I haven't had a chance to read the changeset description. The decision made the API a little less humanistic. I propose it be brought back in SDK 9 for these reasons: 1) The community has two+ years of discovery and documentation around Display#getOrientation. 2) There's no clear reason why applications which don't distinguish between a 90/270 degree rotation should have to implement extra work for forwards/backwards compatibility. 3) The system already decides which side is "top" whether the rotation is 90 or 270 degrees. 4) android.view.Surface has no setRotation(...) method, it uses setOrientation(...). Thus, if Display#getOrientation() was to be deprecated, the same should have happened to Surface#getOrientation for architectural symmetry. 5) Using Display#getOrientation() will always be desired by some applications, whereas Display#getRotation() will always be desired by others.
The frustrating factor here is that on top of the confusion caused by the SDK having different classes/methods to get runtime orientation versus configured orientation, this deprecation is poorly motivated. Yours Truly, Free -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
