Coincidentally(?), just this morning I've come across two examples of SDK features working in API levels where, according to the documentation, they really shouldn't.
The first is Bitmap.setHasAlpha(), which the docs say was just added in API level 12, and which I've certainly never noticed before in nearly 2 years of heavy Bitmap work. However, it seems to be working back to (at least) API level 7 (Android 2.1); it's not working on level 4 (1.x), and I don't have environments for 5 or 6 (2.0x) to test on. The second is the AndroidHttpClient class, documented as level 8 and above, but which I've confirmed to be working fine all the way back to level 3 (1.5)! Possibilities I can imagine: - They're both mis-documented - They existed but were undocumented before the published API levels - ??? In any case, can anyone see a reason not to use them in code which targets API levels earlier than the documented ones? I generally don't hold with using undocumented APIs, on the basis that they might well go away in a later release, but I can't see how that could happen here. It also makes the documentation's "Filter by API level" control much less useful, if it's going to be filtering out stuff I could be using. String -- 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
