|
» 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 » |
« Tips for using the CodeScanner tool! | Main | Help from our Friends »
This week I looked at a couple issues with contextual launching: that's what happens when you hit the Debug button and Carbide determines what to launch in the debugger. Carbide 2.0 is based on the new Eclipse 3.4 release and this includes some new APIs for contextual launching. I added support for those and now when you hover over the Debug button it will show you the exact name of the launch configuration you’ll get, not just the project name. I then looked at bug 3904 which asked that the selection in the Symbian Project Navigator View be used to determine which executable would be used by default. So now if you hit "Debug" while an mmp is selected in the SPN view it will launch the executable built by that mmp by default.