To stop the execution of your application without closing the S60 emulator, press Abort on the progress dialog. Rebuild the debugged application from the IDE and re-launch the application in the emulator. After terminating the debug session, you can leave the emulator running and the DebugAgent waiting for the next MIDlet launch. The first time you launch an application from NetBeans, the emulator starts the Java DebugAgent running to handle the installation and lifecycle of debugged MIDlets. In order to speed up the development cycle, you can keep the emulator running throughout your development session you do not need to restart the emulator for every debug session. The DebugAgent display shows the launch progress (see Figure 5.7) until the MIDlet becomes active and is sent to the foreground. The S60 emulator starts an application called DebugAgent whose role is to manage debug sessions. ![]() If there is more than one MIDlet in your suite, you are asked to choose one of them (see Figure 5.6). When you launch the MIDlet from NetBeans, the progress dialog in Figure 5.5 appears.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |