|
» Subscribe » Favorite Links » What is S60? » Freeware & Trials » S60 devices » Hints and tips » About this blog |
» Blognotes (15) » Bugs and Workarounds (4) » Build tools (5) » Carbide.c++ 1.1 (4) » Carbide.c++ 1.2 (8) » Carbide.c++ 1.3.x (9) » Carbide.c++ 2.0.x (12) » Carbide Plug-Ins (4) » CodeWarrior (2) » FAQ (6) » Future directions (25) » General (48) » Off-topic (5) » On-device debugging (13) » Performance Investigator (2) » Product features (18) » Product releases (16) » Screencast (14) » Support (36) » Tool setup (6) » UI Designer (8) » Usability (18) » Work in Progress (14) » Write-build-debug (4) |
|
» New Remote Connections View » Terminating Multiple Processes » Agile Tuning of the Austin Team » Introduction to the workspace screencast » Adding DLLs while Debugging |
|
Subscribe to RSS feed For email notification, please click here ยป |
« Forgotten, but not Gone | Main | Carbide C++ training »
We do a really cool thing with our launch configuration for the emulator that some developers seem to overllook when they want to debug their application. it wasn't very obvious to users in Carbide 1.3 but it can save users development time. When the user wants to debug their application with Carbide the Symbian OS Emulator launch configuration does not launch the emulator by default but instead launches the executable built by the project.
The main reason we did this was because many users complained about how slow the emulator was to start before they could even launch their application! Also, there can be other problems when keeping the emulator running while creating an application. For example, the emulator locks resource files for some time after exiting out of the application. So if the user changed a resource file he would have to wait for the emulator to release all resources before the user could rebuild his.
This has worked very well for any kits based on Symbian OS developement kit version 9.2 or above.
A Symbian OS Emulator launch configuration created from launch configuration dialog
If for some reason the user wants to launch the emulator first he would have to know to specify the path to epoc.exe.
Launch the emulator by specifying the path to epoc.exe
The alternative way to create an emulator launch configuration is from the Launch Configuration wizard. This is the preferable way to create a launch configuration as it prompts the user for the minimum amount of information needed to correctly create a a launch configuration of a project and allow the user to debug it. It's also easier to launch the wizard as the user only has to press the Debug button in the toolbar from any perspective.
We decided to that to make it more obvious to the user we created the Emulator Launch Configuration wizard to allow the user to specify the executable of his project or the emulator.
New Emulator Launch Configuration wizard
The downside is that it is an extra step the user has to go through before he debugs. So if you don't like it speak up and we'll think of something else. Otherwise, if you don't need to launch your application from the emulator then this will save you time!