CHAPTER 4: Introduction to XML: Defining an Android App, Its Design, and Constants 117You can see the text string modifications you made in the strings.xml file, back in Figure 4-3, in the
ActionBar title, which is now attractively spaced, relative to your application icon. Your app_name
text string now says Hello Universe, rather than HelloUniverse, and your hello_world text string,
which is referenced in your UI design by the TextView UI widget in the activity_main.xml file shown
in Figure 4-1, now gives a more logical greeting for the application relative to the application name.
You can also see the Holo Light OS theme with the Dark ActionBar in this screenshot; this was
defined in the styles.xml file in the /res/values-v14 alternate folder.
The first time that you use the AVD emulator in Eclipse, you will get an Auto Monitor Logcat dialog,
which will ask you if you would like ADT to automatically monitor logcat output error messaging for
your current application. This is a good idea to have available for your application “debugging” or
error eradication work process, so select the “Yes” option and accept the default “error” level of
notification set via the drop-down menu shown at the right side of the dialog in Figure 4-11. I clicked
on the drop-down menu before I took the screenshot, so that you could see the various levels of
error notification that the Android OS can give to you.
Figure 4-11. Setting the ADT Logcat to Auto Monitor error messages
If you look at the error and debugging related tabs at the bottom of Eclipse in one of the screenshots
in this chapter before you select this Logcat monitoring option, such as Figure 4-7 being the most
recent that shows this, you will see that there is no Logcat tab available. After you select this option,
there will be a Logcat tab in Eclipse ADT, as you can see in Figure 4-12 when we begin to edit OS
themes to change your application style.