關於LayoutInflater的佈局問題

問題描述：在用LayoutInflater.inflate 動態佈局時有時會碰到設定的參數無用的問題，以及與與父空間的關係

Before we get started see what LayoutInflater.inflate parameters look like:

• resource: ID for an XML layout resource to load (e.g., R.layout.main_page)
• root: Optional view to be the parent of the generated hierarchy (if attachToRoot is true), or else simply an object that provides a set of LayoutParams values for root of the returned hierarchy (if attachToRoot is false.)
• attachToRoot: Whether the inflated hierarchy should be attached to the root parameter? If false, root is only used to create the correct subclass of LayoutParams for the root view in the XML.
• Returns: The root View of the inflated hierarchy. If root was supplied and attachToRoot is true, this is root; otherwise it is the root of the inflated XML file.

Now for the sample layout and code.

Main layout (main.xml):

<?xml version="1.0" encoding="utf-8"?> <LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" 
android:id="@+id/vertical_container" 
android:orientation="vertical" 
android:layout_width="fill_parent" 
android:layout_height="fill_parent"> </LinearLayout>

Added into this container is a separate TextView, visible as small red square if layout parameters are successfully applied from xml (smallred.xml):

<?xml version="1.0" encoding="utf-8"?> 

<TextView xmlns:android="http://schemas.android.com/apk/res/android" 

android:layout_width="25dip" 

android:layout_height="25dip" 

android:background="#ff0000" android:text="smallred" />

Now LayoutInflater is used with several variations of call parameters

public class InflaterTest extends Activity {

 private View view; 

@Override 

public void onCreate(Bundle savedInstanceState) {

super.onCreate(savedInstanceState); 

setContentView(R.layout.main); 

ViewGroup parent = (ViewGroup) findViewById(R.id.vertical_container); 

// result: layout_height=wrap_content layout_width=match_parent 

view = LayoutInflater.from(getBaseContext()).inflate(R.layout.smallred, null); parent.addView(view); 

// result: layout_height=100 layout_width=100 

view = LayoutInflater.from(getBaseContext()).inflate(R.layout.smallred, null); parent.addView(view, 100, 100); 

// result: layout_height=25dip layout_width=25dip 

// view=textView due to attachRoot=false 

view = LayoutInflater.from(getBaseContext()).inflate(R.layout.smallred, parent, false); parent.addView(view); 

// result: layout_height=25dip layout_width=25dip  // parent.addView not necessary as this is already done by attachRoot=true // view=root due to parent supplied as hierarchy root and attachRoot=true 

view = LayoutInflater.from(getBaseContext()).inflate(R.layout.smallred, parent, true); } }

The actual results of the parameter variations are documented in the code.

SYNOPSIS: Calling LayoutInflater without specifying root leads to inflate call ignoring the layout parameters from the xml. Calling inflate with root not equal null and attachRoot=true does load the layout parameters, but returns the root object again, which prevents further layout changes to the loaded object (unless you can find it using findViewById). The calling convention you most likely would like to use is therefore this one:

loadedView = LayoutInflater.from(getBaseContext()).inflate(R.layout.layout_to_load, parent, false);

To help with layout issues, the hierarchy viewer is highly recommended.

注：引用自http://stackoverflow.com/questions/5026926/making-sense-of-layoutinflater