On Mon, Sep 26, 2011 at 11:13 AM, Rimma Sukhovsky <drim...@gmail.com> wrote: > I did consider that, but that will cause a problem with pre 3.0 devices.
Try ActionBarSherlock, then. > I thought of: > 1. Place the TabHost in a separate Fragment (adding each Tab an empty view), > and place the actual tab content in a second Fragment. That still sounds like you are putting fragments in fragments. If you want to use TabHost in a fragment, that's fine, but the tabs managed by that TabHost should be plain views, not views somehow ripped out of something else (e.g., fragment, activity). -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Warescription: Three Android Books, Plus Updates, One Low Price! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
