Fix: Set the startup object on the app project’s properties page

In the .csproj file, this corresponds to the SilverlightAppEntry element:

<SilverlightAppEntry>PhotoDiary.App</SilverlightAppEntry>

I would call it a bug, that you cannot rename a project and have the SilverlightAppEntry update accordingly. But luckily, the work-around is simple.

Have a nice day!

public class Sneak {
    public static RuntimeException sneakyThrow(Throwable t) {
        if ( t == null ) throw new NullPointerException("t");
        Sneak.<RuntimeException>sneakyThrow0(t);
        return null;
    }

    @SuppressWarnings("unchecked")
    private static <T extends Throwable> void sneakyThrow0(Throwable t) throws T {
        throw (T)t;
    }
}

By using the setContentView(int layoutResId) method of the Activity class your layout will be displayed on the screen. Behind the scenes the Android platform is creating all the view objects contained in your layout xml file provided to the setContentView(int layoutResId) method. This process of creating view objects out of layout resources is referred to as layout inflation.

So far so good. This means that before the setContentView(int layoutResId) method is called the findViewById(int resId) method will return null for any view references in the layout, causing some potential NullpointerExceptions.

@Override
public void onCreate(Bundle savedInstanceState) {
   super.onCreate(savedInstanceState);
 
   EditText addressField = (EditText) findViewById(R.id.address); //To early!! Will return null
   setContentView(R.layout.main);
   Button button = (Button) findViewById(R.id.launchMap);
 
   addressField.setText("Some Text");	//NullPointerException
   button.setText("Some other text");	//No problem
}

To avoid these errors it's a good habit to place the setContentView(int layoutResId) method call at the very top of the onCreate() method.

In some cases you will have to do the layout inflation by yourself, i.e. when you want to set a custom view to a Dialog or a Toast. To inflate a view you use the LayoutInflater class. There's a number of different ways to get a handle to a LayoutInflater:

LayoutInflater inflater = (LayoutInflater)context.getSystemService(
      Context.LAYOUT_INFLATER_SERVICE);
 
LayoutInflater inflater = LayoutInflater.from(context);

To actually create the view object you use the inflate() method of the LayoutInflater. In the most straightforward form this method has the signature:

public View  inflate(int resource, ViewGroup root)

Note that the resource is referring to a layout xml file resource, NOT the id of the view object that you want to inflate. First inflate the layout resource and then get a handle to the view object by using the findViewById(int resId) method.

The second attribute allows you to specify a ViewGroup object to be the root view of the inflated object(s) specified by your layout xml file. This means that the inflated view object(s) are attached as child views on the specified root ViewGroup object. Setting this value to null will simply return the inflated view object(s) without attaching them to a root view.

EditText fooField = (EditText) findViewById(R.id.foo); //To early!! Will return null
LinearLayout myRoot = new LinearLayout();
View itemView = inflater.inflate(R.layout.layout_details, myRoot);  //from layout_details.xml
EditText barField = (EditText) findViewById(R.id.bar); //Now we have an object

In this example the inflate method returns the mRoot object with the view objects contained in the layout_details.xml file attached as child views. So itemView and myRoot is actually referring to the same physical object.