Why not just make the extra image invisible and set it visible when you need it?
On Wed, Apr 14, 2010 at 12:25 PM, ~ TreKing <[email protected]> wrote: > On Wed, Apr 14, 2010 at 12:28 PM, Mark Wyszomierski <[email protected]>wrote: > >> What is the effect of calling setContentView() in an activity twice? >> > > Probably the second call overwrites the first. Why don't you try and find > out? > > >> So layout.a and layout.b are the same, they're a copy-paste of one >> another. B just has >> an extra ImageView appended. >> > > This is terrible. You can reuse layouts by including an existing one in > another. So layout b could just do: > <include:layout.a /> (or whatever the XML syntax is, look it up) > <ImageView /> > > > ------------------------------------------------------------------------------------------------- > TreKing - Chicago transit tracking app for Android-powered devices > http://sites.google.com/site/rezmobileapps/treking > > -- > 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]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Writing code is one of few things that teaches me I don't know everything. Make Call Girl Manager great! Join the forums. http://www.fuligin.com/forums -- 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 To unsubscribe, reply using "remove me" as the subject.
