Hey, that's pretty slick. I hadn't thought of using static inner Activity classes to address this problem. Thanks!
On Wed, May 18, 2011 at 8:21 AM, Zsolt Vasvari <[email protected]> wrote: >> 1. On API Level 11+, use a version of the activity that isn't themed >> as a dialog. I hoped you could use <activity-alias> for this, but it >> doesn't seem like you can override a theme that way... > > > What I do is the following: > > public class MyActivity extends Activity > { > public static class MyActivityNoHolo extends MyActivity > { > // Nothing > } > > > public static class MyActivityHolo extends MyActivity > { > // Nothing > } > } > > > Give them different themes in the manifest and then use the > appropriate class name when starting the activity as determined by the > API level. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 3.6 Available! -- 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

