The only point is that's what I've found to work, nothing more. Perhaps I'm not doing it correctly, but it's like pulling teeth trying to get layouts to work like I want them to, so when I find something that works I'm hard pressed to sit there for hours trying to optimize it 100%.
-- Chris Stewart http://chriswstewart.com On Tue, Mar 22, 2011 at 12:42 AM, Justin Anderson <magouyaw...@gmail.com>wrote: > Maybe it is just me, but what is the point of putting a LinearLayout inside > a RelativeLayout? And for that matter, what is the point of having a > RelativeLayout inside another RelativeLayout that contains only a single > view? > > I don't know really know what the requirements of your app, but you should > be able to achieve the same thing with just a single RelativeLayout and all > your other fragments/views inside of that... > > One of the big advantages of RelativeLayout is that there is less need for > nesting layouts... > > Thanks, > Justin Anderson > MagouyaWare Developer > http://sites.google.com/site/magouyaware > > > On Mon, Mar 21, 2011 at 9:28 PM, Chris Stewart <cstewart...@gmail.com>wrote: > >> I wanted to follow up on this question. I got it working tonight by using >> RelativeLayout. The overall design is as such: >> >> RelativeLayout >> -- LinearLayout >> -- Fragment A >> -- Fragment B >> -- Fragment C >> -- /LinearLayout >> -- RelativeLayout (with android:layout_alignParentBottom="true") >> -- TextView >> -- /RelativeLayout >> /RelativeLayout >> >> -- >> Chris Stewart >> http://chriswstewart.com >> >> >> >> On Mon, Mar 21, 2011 at 4:07 PM, Chris Stewart <cstewart...@gmail.com>wrote: >> >>> I'm working on a Honeycomb app and I'd like to have a scrolling ticker at >>> the bottom of the screen. I did something similar with a phone app, where I >>> effectively had a LinearLayout that took up the bottom of the screen and >>> contained a TextView inside of it. I attempted to reuse that code in this >>> situation and couldn't get the Layout or TextView to display. The only real >>> differences here are the use of Android 3.0 and fragments in the layout >>> file. >>> >>> Unfortunately I'm at work, so I'm unable to post the specific code in >>> question. But, I wanted to see if anyone has already encountered this while >>> working with Android 3.0/fragments or if you've seen an example somewhere >>> online I can explore for answers. >>> >>> -- >>> Chris Stewart >>> http://chriswstewart.com >>> >>> >> -- >> 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 >> > > -- > 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 -- 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
