A (175)

(Tuis.) #1

218 CHAPTER 7: Making Apps Interactive: Intents, Event Handling, and Menus


My logic here in performing this work process is that somehow this “snapshot” of the app which
was being saved (between subsequent launches of the AVD) had become corrupt, or otherwise was
causing some sort of bug or error that was preventing the AVD emulator from continuing the part of
its launch which accesses the app project (and icon) from Eclipse.


Thus, to allow me to do an “end-run” around this particular problem, I utilize the AVD Manager’s
Start button, in order to allow me to access this Launch Options dialog, so that I can disable these
snapshot features. The Launch Options dialog allows me to be able to force a “fresh” AVD launch
into system memory of whichever AVD emulator I wish to test with.


If the Android OS (or AVD) developers fix this particular AVD issue, which you at some point in time
will most likely encounter in your Android app development work process, then this work process
will no longer become necessary to fix this quagmire. However, I thought it wise to advise you
regarding this work process, and my implementation logic behind it, in case you encounter this
problem, and it brings you to a grinding halt in the application development coding-testing cycle! If
you can’t get your application to launch in the emulator, you can’t test it as you develop it; thus, this
is an important topic.


Once the animated Android logo stops loading the AVD into memory, you will see the screen shown
on the left side of Figure 7-4. Click and drag the lock icon outward, until it circumscribes a circle,
and then release it. After you do this your application (and your new menu structure) will auto-launch
again, as is shown on the right side of Figure 7-4.


Figure 7-4. Drag to unlock the Nexus One; click the ActionBar options menu (three vertical dots) to open the menu

Free download pdf