Android Layout: Merge how to position an include?

Well, the merge tag was created to defeat the extra complexity that is being created in the view hierarchy for the sake of simplicity in your layout definition XML If you refer to the merge explanation page you will see how the TextView that is added before the frame layout occupies some space. The rest of the space is automatically filled with a FrameLayout so that the available free space has concrete bounds at any point of time. If we add another Layout that takes up that space, then the automatically created FrameLayout becomes useless.

The tag solves that by adding children to the automatically created FrameLayout as if that layout has been declared in our XML And that is the purpose of the merge tag In your case, you probably need a RelativeLayout as your application obviously requires more complexity. I believe the merge tag is not the solution for you.

Well, the merge tag was created to defeat the extra complexity that is being created in the view hierarchy for the sake of simplicity in your layout definition XML. If you refer to the merge explanation page, you will see how the TextView that is added before the frame layout occupies some space. The rest of the space is automatically filled with a FrameLayout, so that the available free space has concrete bounds at any point of time.

If we add another Layout, that takes up that space, then the automatically created FrameLayout becomes useless. The tag solves that by adding children to the automatically created FrameLayout as if that layout has been declared in our XML. And that is the purpose of the tag.In your case, you probably need a RelativeLayout, as your application obviously requires more complexity.

I believe the tag is not the solution for you.

Well, the merge tag was created to defeat the extra complexity that is being created in the view hierarchy for the sake of simplicity in your layout definition XML. If you refer to the merge explanation page, you will see how the TextView that is added before the frame layout occupies some space. The rest of the space is automatically filled with a FrameLayout, so that the available free space has concrete bounds at any point of time.

If we add another Layout, that takes up that space, then the automatically created FrameLayout becomes useless. The tag solves that by adding children to the automatically created FrameLayout as if that layout has been declared in our XML. And that is the purpose of the tag.

In your case, you probably need a RelativeLayout, as your application obviously requires more complexity. I believe the tag is not the solution for you.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Related Questions