Introduction in Getting Started

Type	State	Explanation
Enabled	Unresolved	Indicates that the breakpoint is currently enabled but not located in the executable during a debug session. Debugger cannot halt program execution.
Enabled	Resolved	Indicates that the breakpoint is currently enabled and resolved for the source line. The debugger halts program execution at an enabled breakpoint.
Disabled	Unresolved	Indicates that the breakpoint is currently disabled but not located in the executable during a debug session. The debugger does not halt program execution at a disabled breakpoint.
Disabled	Resolved	Indicates that the breakpoint is currently disabled and resolved for the source line. The debugger does not halt program execution at a disabled breakpoint.

Type	State	Explanation
Enabled	Unresolved	Indicates that the breakpoint is currently enabled but not located in the executable during a debug session. Debugger cannot halt program execution.
Enabled	Resolved	Indicates that the breakpoint is currently enabled and resolved for the source line. The debugger halts program execution at an enabled breakpoint.
Disabled	Unresolved	Indicates that the breakpoint is currently disabled but not located in the executable during a debug session. The debugger does not halt program execution at a disabled breakpoint.
Disabled	Resolved	Indicates that the breakpoint is currently disabled and resolved for the source line. The debugger does not halt program execution at a disabled breakpoint.

Project Type	Available Templates
Generic Symbian OS	- Basic console application (EXE) - used for any SDK - Basic dynamically linked library (DLL) - used for any SDK - Basic static library (LIB) - used for any SDK - Empty Project for Symbian - empty project with minimal bld.inf and MMP and no sources or libraries. For advanced users only. -
S60	- GUI Application - GUI Application with UI Designer - Open C Console application - project template based on industry-standard POSIX and middleware C libraries for S60 -
Tutorials	- S60 Birthday Tutorial with UI Designer - S60 Yahoo! Image Search Tutorial with UI Designer -

Project Type	Available Templates
Generic Symbian OS	+ Basic console application (EXE) - used for any SDK + Basic dynamically linked library (DLL) - used for any SDK + Basic static library (LIB) - used for any SDK + Empty Project for Symbian - empty project with minimal bld.inf and MMP and no sources or libraries. For advanced users only. +
S60	+ GUI Application + GUI Application with UI Designer + Open C Console application - project template based on industry-standard POSIX and middleware C libraries for S60 +
Tutorials	+ S60 Birthday Tutorial with UI Designer + S60 Yahoo! Image Search Tutorial with UI Designer +

Option	Description	Default
Breakpoint List	Select the breakpoints and watchpoints that you wish to export, and deselect those that you do not.	not selected
To file	The file to export the breakpoints and watchpoints to, you can also click Browse... to search for a location to export.	There can be two possible defaults: - - If you have never exported breakpoints or watchpoints before it will be blank - If you have exported breakpoints and watchpoints before the last file name you exported to will be automatically inserted. -
Overwrite existing file without warning	- When selected, if the file you wish to export to already exists, it will be overwritten automatically by the wizard. -	not selected

Option	Description	Default
Breakpoint List	Select the breakpoints and watchpoints that you wish to export, and deselect those that you do not.	not selected
To file	The file to export the breakpoints and watchpoints to, you can also click Browse... to search for a location to export.	There can be two possible defaults: + + If you have never exported breakpoints or watchpoints before it will be blank + If you have exported breakpoints and watchpoints before the last file name you exported to will be automatically inserted. +
Overwrite existing file without warning	+ When selected, if the file you wish to export to already exists, it will be overwritten automatically by the wizard. +	not selected

Option	Description
From file	Enter the file name to import or click Browse to search for a .bkpt file to import.
Update existing breakpoints	- Update all existing project breakpoints found in the imported breakpoint data file. -
Create breakpoint working sets	Create a new breakpoint working set containing the imported breakpoint data.

Option	Description
From file	Enter the file name to import or click Browse to search for a .bkpt file to import.
Update existing breakpoints	+ Update all existing project breakpoints found in the imported breakpoint data file. +
Create breakpoint working sets	Create a new breakpoint working set containing the imported breakpoint data.

Property	Explanation
Class	Breakpoint class
Type	Breakpoint type. Regular is the default software breakpoint type.
File	The complete path and filename of the file where the breakpoint is located.
Line number	The breakpoints line number in the file.
Enabled	Indicates the current status of the breakpoint. When checkmarked, the breakpoint stops program execution if its condition is met. When unchecked, the breakpoint is ignored during the debug session.
Condition	The conditional expression associated with the item. This conditional expression must evaluate to true in order for the item to perform its specified action. If left blank, execution is suspended each time the breakpoint is hit. If a condition is entered,like n==10, execution only stops when the condition evaluates to true.
Ignore count	Defines when a breakpoint should be ignored during a debug session. The default count 0 indicates that the breakpoint should suspend execution each time it is hit. A value of 1 defines this breakpoint as a temporary breakpoint, which should be ignored after the first time it is encountered. -

Property	Explanation
Class	Breakpoint class
Type	Breakpoint type. Regular is the default software breakpoint type.
File	The complete path and filename of the file where the breakpoint is located.
Line number	The breakpoints line number in the file.
Enabled	Indicates the current status of the breakpoint. When checkmarked, the breakpoint stops program execution if its condition is met. When unchecked, the breakpoint is ignored during the debug session.
Condition	The conditional expression associated with the item. This conditional expression must evaluate to true in order for the item to perform its specified action. If left blank, execution is suspended each time the breakpoint is hit. If a condition is entered,like n==10, execution only stops when the condition evaluates to true.
Ignore count	Defines when a breakpoint should be ignored during a debug session. The default count 0 indicates that the breakpoint should suspend execution each time it is hit. A value of 1 defines this breakpoint as a temporary breakpoint, which should be ignored after the first time it is encountered. +

Type	Icon	State	Explanation
Enabled		Unresolved	The breakpoint is enabled but the symbols for the module are not loaded or the breakpoint was not able to be set within the current function.Breakpoint icon remains in unflagged state indicating unresolved status. - If the breakpoint has been set in the source file but not resolved: - - a debug session has not been launched to resolve the breakpoint. For example, you just set the breakpoint and have yet to launch a debug session. - the symbols file containing the breakpoint cannot be found. Ensure the module to debug is present in the Executable view list so the debugger can locate and load the executable for symbol resolution. - breakpoint is set on a source line without any executable code - breakpoint is located in a deadstripped function not present in the executable -
	Resolved	The breakpoint is currently enabled, the symbols for the module are loaded, and the breakpoint located in the executable being debugged. The debugger halts program execution at an enabled breakpoint. - - resolved — the symbols for the module are loaded and the breakpoint located in the executable that’s currently being debugged, circle icon changes to flagged icon - resolved and moved —the breakpoint is not found in the executable at the specified point. Debugger moves breakpoint forward in the current function until a line is found that can be resolved. Breakpoint icon moved to source line matching new breakpoint location and changed to flagged icon - -
Disabled		Unresolved	Indicates that the breakpoint is currently disabled but not located in the executable during a debug session. The debugger does not halt program execution at a disabled breakpoint.
	Resolved	Indicates that the breakpoint is currently disabled and resolved for the source line. The debugger does not halt program execution at a disabled breakpoint.

Type	Icon	State	Explanation
Enabled		Unresolved	The breakpoint is enabled but the symbols for the module are not loaded or the breakpoint was not able to be set within the current function.Breakpoint icon remains in unflagged state indicating unresolved status. + If the breakpoint has been set in the source file but not resolved: + + a debug session has not been launched to resolve the breakpoint. For example, you just set the breakpoint and have yet to launch a debug session. + the symbols file containing the breakpoint cannot be found. Ensure the module to debug is present in the Executable view list so the debugger can locate and load the executable for symbol resolution. + breakpoint is set on a source line without any executable code + breakpoint is located in a deadstripped function not present in the executable +
	Resolved	The breakpoint is currently enabled, the symbols for the module are loaded, and the breakpoint located in the executable being debugged. The debugger halts program execution at an enabled breakpoint. + + resolved — the symbols for the module are loaded and the breakpoint located in the executable that’s currently being debugged, circle icon changes to flagged icon + resolved and moved —the breakpoint is not found in the executable at the specified point. Debugger moves breakpoint forward in the current function until a line is found that can be resolved. Breakpoint icon moved to source line matching new breakpoint location and changed to flagged icon + +
Disabled		Unresolved	Indicates that the breakpoint is currently disabled but not located in the executable during a debug session. The debugger does not halt program execution at a disabled breakpoint.
	Resolved	Indicates that the breakpoint is currently disabled and resolved for the source line. The debugger does not halt program execution at a disabled breakpoint.

Item	Icon	Explanation
Remove Selected Breakpoint		Removes the selected breakpoint from the breakpoints list.
Remove All Breakpoints		Removes all breakpoints from the breakpoints list.
Show Breakpoints Supported by Selected Target		Limits the breakpoints shown to only those supported in the current target.
Go to File for Breakpoint		Displays the breakpoint in an editor view, opening the source file if required.
Skip All Breakpoints		Toggles the debugger to skip all breakpoints regardless of their current enabled or disabled state, or hit all breakpoints.
Expand All		Expand all matches in the hierarchical view.
Collapse All		Collapse all matches in the hierarchical view.
Link with Debug View		When enabled, the breakpoint shown in the editor view is also highlighted in the Breakpoints view. When disabled, the breakpoint selected in the Breakpoints view does not change.
Menu		Click to display additional Breakpoints view options for paths, grouping choices, and working sets as shown below. -

Item	Explanation
Go to File	Opens the associated file for the breakpoint in an editor, make it active and highlight the breakpoint location. If the file is already open, make it active and the highlight the breakpoint location.
Enable	Enables the selected breakpoints.
Disable	Disables the selected breakpoints.
Remove	Removes the selected breakpoints from the project and Breakpoints view.
Remove All	Removes all breakpoints from the project and Breakpoints view.
Select All	Selects all the breakpoints shown in the Breakpoints view.
Copy	Copies the selected breakpoint to the clipboard.
Paste	Always disabled.
Export Breakpoints	Opens the Export Breakpoints wizard to store the project's breakpoint data.
Import Breakpoints	Opens the Import Breakpoints wizard to import stored breakpoint data (.bkpt).
Add Watchpoint (C/C++)...
Properties	Opens the Properties for Breakpoint dialog.

Item	Icon	Explanation
Remove Selected Breakpoint		Removes the selected breakpoint from the breakpoints list.
Remove All Breakpoints		Removes all breakpoints from the breakpoints list.
Show Breakpoints Supported by Selected Target		Limits the breakpoints shown to only those supported in the current target.
Go to File for Breakpoint		Displays the breakpoint in an editor view, opening the source file if required.
Skip All Breakpoints		Toggles the debugger to skip all breakpoints regardless of their current enabled or disabled state, or hit all breakpoints.
Expand All		Expand all matches in the hierarchical view.
Collapse All		Collapse all matches in the hierarchical view.
Link with Debug View		When enabled, the breakpoint shown in the editor view is also highlighted in the Breakpoints view. When disabled, the breakpoint selected in the Breakpoints view does not change.
Menu		Click to display additional Breakpoints view options for paths, grouping choices, and working sets as shown below. +

Item	Explanation
Go to File	Opens the associated file for the breakpoint in an editor, make it active and highlight the breakpoint location. If the file is already open, make it active and the highlight the breakpoint location.
Enable	Enables the selected breakpoints.
Disable	Disables the selected breakpoints.
Remove	Removes the selected breakpoints from the project and Breakpoints view.
Remove All	Removes all breakpoints from the project and Breakpoints view.
Select All	Selects all the breakpoints shown in the Breakpoints view.
Copy	Copies the selected breakpoint to the clipboard.
Paste	Always disabled.
Export Breakpoints	Opens the Export Breakpoints wizard to store the project's breakpoint data.
Import Breakpoints	Opens the Import Breakpoints wizard to import stored breakpoint data (.bkpt).
Add Watchpoint (C/C++)...
Properties	Opens the Properties for Breakpoint dialog.

Item	Icons	Explanation
Show Type Names		Toggles the display of type names in the Expressions view.
Show Logical Structure		Not available in C/C++ yet.
Collapse All		Collapses all expanded expressions into the top level.
Remove Selected Expression		Click to remove all currently selected expressions from the expressions list.
Remove All Expressions		Click to remove all expressions from the expressions list.

Item	Explanation
Select All	Selects all the expressions shown in the Expressions view.
Copy Expressions	Copies the selected expressions to the clipboard.
Remove	Remove the selected expressions from the Expressions view list.
Remove All	Remove all expressions from the Expressions view list.
Find...	Opens a Find dialog to search the Expressions view list.
Change Value...	Opens the Set Value dialog where you can modify the value assigned to the selected expressions. Change the value and click OK. -
Add Watch Expression...	Opens the Add Watch Exression dialog for creation of a new expression. -
Disable	Disables automatic evaluation of the selected expression and appends (disabled) to the expression name. Useful when you have lots of expressions but are concentrating on only a few. The more expressions that need evaluaton, the longer it takes to update the Expressions view.
Enable	Enables automatic evaluation of the selected expression. Enables a disabled expression so that it is evaluated during the debug session.
Edit Watch Expression...	Opens the Edit Watch Expression dialog where you can modify the expression and enable it for automatic evaluation.
Reevaluate Watch Expression	Forces the expression to be reevaluated. Useful after the expressions has been edited or not evaluated due to being disabled.

Item	Icons	Explanation
Show Type Names		Toggles the display of type names in the Expressions view.
Show Logical Structure		Not available in C/C++ yet.
Collapse All		Collapses all expanded expressions into the top level.
Remove Selected Expression		Click to remove all currently selected expressions from the expressions list.
Remove All Expressions		Click to remove all expressions from the expressions list.

Item	Explanation
Select All	Selects all the expressions shown in the Expressions view.
Copy Expressions	Copies the selected expressions to the clipboard.
Remove	Remove the selected expressions from the Expressions view list.
Remove All	Remove all expressions from the Expressions view list.
Find...	Opens a Find dialog to search the Expressions view list.
Change Value...	Opens the Set Value dialog where you can modify the value assigned to the selected expressions. Change the value and click OK. +
Add Watch Expression...	Opens the Add Watch Exression dialog for creation of a new expression. +
Disable	Disables automatic evaluation of the selected expression and appends (disabled) to the expression name. Useful when you have lots of expressions but are concentrating on only a few. The more expressions that need evaluaton, the longer it takes to update the Expressions view.
Enable	Enables automatic evaluation of the selected expression. Enables a disabled expression so that it is evaluated during the debug session.
Edit Watch Expression...	Opens the Edit Watch Expression dialog where you can modify the expression and enable it for automatic evaluation.
Reevaluate Watch Expression	Forces the expression to be reevaluated. Useful after the expressions has been edited or not evaluated due to being disabled.

Item	Icons	Explanation
Show Type Names		Toggles the display of type names in the Variables view.
Show Logical Structure		Not available in C/C++ yet.
Collapse All		Collapses all expanded variables into the top level.
Add Global Variables		Click to open the Global Variables dialog where you can select one or more global variables to display in the Variables view. Global variables appear at the top of the variables list.
Remove Selected Global Variables		Click to remove all currently selected global variables from the variables list.
Remove All Global Variables		Click to remove all global variables from the variables list.
Menu		Enables you to modifiy the Layout to change the view orientation between: horizontal, vertical, or variables pane only. - In addition, use Show All Variables to toggle between showing only those variables that are in scope and live or show all local variables, even if redundant. With this option on you will see all of the variables including the multiple defined variables like “i” for your loops and ones that may no longer have accurate values.

Item	Explanation
Select All	Selects all the variables shown in the Variables view.
Copy Variables	Copies the selected variables to the clipboard.
Enable	Enables the selected variable.
Disable	Disables the selected variable.
Display as Array...
Cast To Type...	Opens the Cast to Type dialog where you can assign a new type to the variable.
Restore Original Type	Resets the selected variable to the original type assigned by the program.
View Memory	Opens a Memory view on the selected variable so you can examine it.
Find...	Opens a Find dialog to search for variables.
Change Value...	Opens the Set Value dialog where you can modify the value assigned to the selected variable. Change the value and click OK. -
Add Watchpoint (C/C++)...	Opens the Add Watchpoint dialog enabling you to define a watchpoint on the variable.
Add Global Variables...	Select to open the Global Variables dialog where you can select one or more global variables to display in the Variables view. Global variables appear at the top of the variables list.
Remove Global Variables	Remove the selected global variables from the Variables view.
Remove All Global Variables	Remove all global variables from the Variables view.
Create Watch Expression	Creates a watchpoint on the selected variable and displays it in the Watchpoint view.
Format	Change the selected variable's display format. The default setting is Natural, or the format assigned when the variable is defined. For example, the decimal value of 256 would appear as: - - Binary (0b100000) - Natural (256) - Decimal (256) - Hexadecimal (0x100) -

Item	Icons	Explanation
Show Type Names		Toggles the display of type names in the Variables view.
Show Logical Structure		Not available in C/C++ yet.
Collapse All		Collapses all expanded variables into the top level.
Add Global Variables		Click to open the Global Variables dialog where you can select one or more global variables to display in the Variables view. Global variables appear at the top of the variables list.
Remove Selected Global Variables		Click to remove all currently selected global variables from the variables list.
Remove All Global Variables		Click to remove all global variables from the variables list.
Menu		Enables you to modifiy the Layout to change the view orientation between: horizontal, vertical, or variables pane only. + In addition, use Show All Variables to toggle between showing only those variables that are in scope and live or show all local variables, even if redundant. With this option on you will see all of the variables including the multiple defined variables like “i” for your loops and ones that may no longer have accurate values.

Item	Explanation
Select All	Selects all the variables shown in the Variables view.
Copy Variables	Copies the selected variables to the clipboard.
Enable	Enables the selected variable.
Disable	Disables the selected variable.
Display as Array...
Cast To Type...	Opens the Cast to Type dialog where you can assign a new type to the variable.
Restore Original Type	Resets the selected variable to the original type assigned by the program.
View Memory	Opens a Memory view on the selected variable so you can examine it.
Find...	Opens a Find dialog to search for variables.
Change Value...	Opens the Set Value dialog where you can modify the value assigned to the selected variable. Change the value and click OK. +
Add Watchpoint (C/C++)...	Opens the Add Watchpoint dialog enabling you to define a watchpoint on the variable.
Add Global Variables...	Select to open the Global Variables dialog where you can select one or more global variables to display in the Variables view. Global variables appear at the top of the variables list.
Remove Global Variables	Remove the selected global variables from the Variables view.
Remove All Global Variables	Remove all global variables from the Variables view.
Create Watch Expression	Creates a watchpoint on the selected variable and displays it in the Watchpoint view.
Format	Change the selected variable's display format. The default setting is Natural, or the format assigned when the variable is defined. For example, the decimal value of 256 would appear as: + + Binary (0b100000) + Natural (256) + Decimal (256) + Hexadecimal (0x100) +

Name	Description
Expression to watch	If not already entered, you can enter any arbitrary memory location for watching.
Memory space	Not supported.
Units	Define the size of the units to monitor. This setting defaults to the size of the variable to watch. If an arbitrary memory address is entered, then the default unit size is set to 1 byte. Once you enable the units checkbox, you're must enter a value for it.
Access: Write/Read	Check the appropriate access type to trigger the watchpoint for the specified memory location. This setting is shown as a unique icon in the Breakpoints view next to the listed watchpoint. The following list shows the resolved version of the icons used to indicate the type of watchpoint set: - - Read only () - Write only () - Read/Write () -

Name	Description
Expression to watch	If not already entered, you can enter any arbitrary memory location for watching.
Memory space	Not supported.
Units	Define the size of the units to monitor. This setting defaults to the size of the variable to watch. If an arbitrary memory address is entered, then the default unit size is set to 1 byte. Once you enable the units checkbox, you're must enter a value for it.
Access: Write/Read	Check the appropriate access type to trigger the watchpoint for the specified memory location. This setting is shown as a unique icon in the Breakpoints view next to the listed watchpoint. The following list shows the resolved version of the icons used to indicate the type of watchpoint set: + + Read only () + Write only () + Read/Write () +

Watchpoint	Resolved	Unresolved
Enabled	Stops execution	No
Disabled	No	No

Type	State	Icon	Explanation
Write	enabled		The watchpoint is activated for write access operations on the specific memory location and if resolved, will halt program execution on a write operation at the watchpoint.
disabled		Watchpoint is disabled for the source line, debugger does not halt program execution on a write operation.
Read	enabled		The watchpoint is activated for read access operations on the specific memory location and if resolved, will halt program execution on a read operation at the watchpoint.
disabled		Watchpoint is disabled for the source line, debugger does not halt program execution on a read operation.
Write/Read	enabled		The watchpoint is activated for both read and write access operations on the specific memory location and if resolved, will halt program execution on any read or write operation at the watchpoint.
disabled		Watchpoint is disabled for the source line, debugger does not halt program execution on a read or write operation.

Watchpoint	Resolved	Unresolved
Enabled	Stops execution	No
Disabled	No	No

Type	State	Icon	Explanation
Write	enabled		The watchpoint is activated for write access operations on the specific memory location and if resolved, will halt program execution on a write operation at the watchpoint.
disabled		Watchpoint is disabled for the source line, debugger does not halt program execution on a write operation.
Read	enabled		The watchpoint is activated for read access operations on the specific memory location and if resolved, will halt program execution on a read operation at the watchpoint.
disabled		Watchpoint is disabled for the source line, debugger does not halt program execution on a read operation.
Write/Read	enabled		The watchpoint is activated for both read and write access operations on the specific memory location and if resolved, will halt program execution on any read or write operation at the watchpoint.
disabled		Watchpoint is disabled for the source line, debugger does not halt program execution on a read or write operation.

Item	Explanation
Serial Port	Select the serial port option to use for this launch or launch configuration. Once set, this port will be used for all subsequent launch configurations until it is set again. Note that for USB and BT can be dynamically assigned, so its critical that the port ID assigned here matches the one the system is using to communicate with the target device. - If you are using a USB connection, the connected phone's name should appear in the menu to help identify which port is being used.
Baud Rate	Use the Baud Rate option to select the baud rate for communication. The default baud rate value is 115200 bits per second (bps).
Data Bits	Use the Data Bits option to select a common data bits size (4, 5, 6, 7, and 8). The default data bits value is 8.
Parity	Use the Parity option to select the parity setting (None, Odd, or Even). The default parity value is None.
Stop Bits	Use the Stop Bits option to select the stop bits setting (1, 1.5, 2). The default stop bits value is 1.
Flow Control	Use the Flow Control option to select the flow control setting (None, Hardware (RTS/CTS), and Software (XON/XOFF)). The default flow control value is None.

Item	Explanation
Serial Port	Select the serial port option to use for this launch or launch configuration. Once set, this port will be used for all subsequent launch configurations until it is set again. Note that for USB and BT can be dynamically assigned, so its critical that the port ID assigned here matches the one the system is using to communicate with the target device. + If you are using a USB connection, the connected phone's name should appear in the menu to help identify which port is being used.
Baud Rate	Use the Baud Rate option to select the baud rate for communication. The default baud rate value is 115200 bits per second (bps).
Data Bits	Use the Data Bits option to select a common data bits size (4, 5, 6, 7, and 8). The default data bits value is 8.
Parity	Use the Parity option to select the parity setting (None, Odd, or Even). The default parity value is None.
Stop Bits	Use the Stop Bits option to select the stop bits setting (1, 1.5, 2). The default stop bits value is 1.
Flow Control	Use the Flow Control option to select the flow control setting (None, Hardware (RTS/CTS), and Software (XON/XOFF)). The default flow control value is None.

Item	Explanation
Exceptions to catch	Click to enable by exception which x86 exceptions the debugger should catch.
Check All	Enables catching all exceptions.
Clear All	Disables catching all exceptions.

Item	Explanation
Exceptions to catch	Click to enable by exception which x86 exceptions the debugger should catch.
Check All	Enables catching all exceptions.
Clear All	Disables catching all exceptions.

Item	Explanation
Load symbols for these executables and target them for debugging	Select the rule which governs the executable support used by this project for debugging. The options include: - - Executables in the workspace from this SDK — shows all executables in the workspace built using the specified SDK. This is the default setting. - Executables built by this project — shows only the executables built by this project using the specified SDK - Executables selected below — shows only the executables chosen by the user. Initial list display uses the All Executables listing. - All executables (slows launch) — shows all the executables in the workspace regardless of which SDK created them. Selecting this option will slow down Carbide launches as the list is populated. -
Executables list	Shows all the executables associated with this project.
Add...	Opens the Select an executable file dialog which can locate and select executable files and add them to the project's executables list.
Select All	Enables all the executables in the list for debugging.
Unselect All	Disables all the executables in the list from debugging.

Item	Explanation
Load symbols for these executables and target them for debugging	Select the rule which governs the executable support used by this project for debugging. The options include: + + Executables in the workspace from this SDK — shows all executables in the workspace built using the specified SDK. This is the default setting. + Executables built by this project — shows only the executables built by this project using the specified SDK + Executables selected below — shows only the executables chosen by the user. Initial list display uses the All Executables listing. + All executables (slows launch) — shows all the executables in the workspace regardless of which SDK created them. Selecting this option will slow down Carbide launches as the list is populated. +
Executables list	Shows all the executables associated with this project.
Add...	Opens the Select an executable file dialog which can locate and select executable files and add them to the project's executables list.
Select All	Enables all the executables in the list for debugging.
Unselect All	Disables all the executables in the list from debugging.

Item	Explanation
File transfer list	The File transfer list displays the project files that are moved to the target device for launch and debugging purposes. It contains these columns: - - Enabled—a checkmark indicates that the IDE should transfer the specified file to the target directory. If unchecked, do not transfer the file. - File to transfer—the path and filename to a file on the host machine to be transfered - Target directory—the path to the target directory where transfered files are placed on the device. - - - The target directories where files can be installed depends upon the type of device image you have on the device and which version of TRK you are using. - - Application TRK - public folders only on production device images - System TRK - public and protected folders, like c:\sys\bin, on RnD device images - -
Add	Click to add a file to the file transfer list.
Edit...	Click to edit the selected file in the file transfer list.
Remove	Click to remove the selected file from the file transfer list.

Item	Explanation
File transfer list	The File transfer list displays the project files that are moved to the target device for launch and debugging purposes. It contains these columns: + + Enabled—a checkmark indicates that the IDE should transfer the specified file to the target directory. If unchecked, do not transfer the file. + File to transfer—the path and filename to a file on the host machine to be transfered + Target directory—the path to the target directory where transfered files are placed on the device. + + + The target directories where files can be installed depends upon the type of device image you have on the device and which version of TRK you are using. + + Application TRK - public folders only on production device images + System TRK - public and protected folders, like c:\sys\bin, on RnD device images + +
Add	Click to add a file to the file transfer list.
Edit...	Click to edit the selected file in the file transfer list.
Remove	Click to remove the selected file from the file transfer list.

Item	Explanation
Installation file -	Enter the complete path to the .sis or .pkg file to install on the target device or click Browse to use the standard file selection dialog.
Download directory	The directory on the target device to download the file into before installing it. The default directory value is C:\data\.
Install each launch even if installer file has not changed	Enable this option to force an update of the installed file even if no changes have been detected. This ensures a clean program install for each debug session.
Do not show installer UI on the phone	Use this option to specify if the installer UI on the target device is shown when installing the file. Disabling this option may require interaction with the installer UI on the target device, slowing down the install process. The default setting is on.
Install to drive	A list of common drives where files may be installed to. The default drive setting is C.
Partial upgrade sis/sisx path	Shows the path to the partial upgrade SIS file once it has been created.
Open SIS Builder settings...	Click to open the SIS Builder page of the Carbide Build Configurations properties panel where you can enable the partial upgrade feature for subsequent builds.

Item	Explanation
Installation file +	Enter the complete path to the .sis or .pkg file to install on the target device or click Browse to use the standard file selection dialog.
Download directory	The directory on the target device to download the file into before installing it. The default directory value is C:\data\.
Install each launch even if installer file has not changed	Enable this option to force an update of the installed file even if no changes have been detected. This ensures a clean program install for each debug session.
Do not show installer UI on the phone	Use this option to specify if the installer UI on the target device is shown when installing the file. Disabling this option may require interaction with the installer UI on the target device, slowing down the install process. The default setting is on.
Install to drive	A list of common drives where files may be installed to. The default drive setting is C.
Partial upgrade sis/sisx path	Shows the path to the partial upgrade SIS file once it has been created.
Open SIS Builder settings...	Click to open the SIS Builder page of the Carbide Build Configurations properties panel where you can enable the partial upgrade feature for subsequent builds.

Item	Explanation
Parse Rom Log File	Check this option to parse the ROM log file.
Symbian Rom Log File	Enter or browse to the Rom log file that is generated when the Symbian OS image is built. This is necessary for debugging any Symbian OS module.
Symbian Epoc32 Directory	Enter or browse to the epoc32 directory for the Symbian OS kit that is being targeted for debugging. This is necessary for the debugger to resolve the full paths for each module in the log file since the log file does not contain the full paths.
Log unresolved modules	Check this option to log unresolved modules. If the actual binary in the log file doesn’t exist on the PC, then a warning message will be logged in a Rom Log console window.
Debug non-XIP executables	Check this option to target non-XIP executables. This allows the debugger to target a non-XIP module whenever it’s loaded.
Download Rom Image	Check this box to enable downloading.
Symbian Rom Image	Enter or browse to the Symbian OS image (.img file) that will be downloaded onto the target at the specified download address.
Download Address (hex)	Specify the address where the image is to be downloaded. This address is target-specific. The address should be in hexadecimal format with the 0x prefix.
Same as start address	Check this option to make the download address the same as the start address.
Ask for download at the start of each debug session	Select this option to prompt you to download the image at the start of the debug session.

Item	Explanation
Parse Rom Log File	Check this option to parse the ROM log file.
Symbian Rom Log File	Enter or browse to the Rom log file that is generated when the Symbian OS image is built. This is necessary for debugging any Symbian OS module.
Symbian Epoc32 Directory	Enter or browse to the epoc32 directory for the Symbian OS kit that is being targeted for debugging. This is necessary for the debugger to resolve the full paths for each module in the log file since the log file does not contain the full paths.
Log unresolved modules	Check this option to log unresolved modules. If the actual binary in the log file doesn’t exist on the PC, then a warning message will be logged in a Rom Log console window.
Debug non-XIP executables	Check this option to target non-XIP executables. This allows the debugger to target a non-XIP module whenever it’s loaded.
Download Rom Image	Check this box to enable downloading.
Symbian Rom Image	Enter or browse to the Symbian OS image (.img file) that will be downloaded onto the target at the specified download address.
Download Address (hex)	Specify the address where the image is to be downloaded. This address is target-specific. The address should be in hexadecimal format with the 0x prefix.
Same as start address	Check this option to make the download address the same as the start address.
Ask for download at the start of each debug session	Select this option to prompt you to download the image at the start of the debug session.

Item	Explanation
Parse Rom Log File	Activate the Parse ROM Log File option and specify the information that the debugger needs in order to show detailed stack information, set breakpoints, and show source level debugging information for ROM images.
Symbian Rom Log File	In the Symbian Rom Log File text field, browse to or enter the full path and name of the log file that corresponds to the ROM image on the target device. This log file is generated by default when the ROM image is built.
Symbian Epoc32 Directory	Specifies the epoc32 directory in which the ROM image and log files are stored. Since the log file may not contain full paths to the ROM components on the host PC, you need to enter this epoc32 directory. - NOTE Always include the epoc32 folder in this path.
Log unresolved modules	Activate the Log unresolved modules option to have the debugger output a list of components from the specified ROMBUILD log file that do not have debugger symbolic information. The list is displayed in the debugger console window at the beginning of the debug session. - NOTE You cannot perform source-level debugging on components that do not include symbolic information.

Item	Explanation
Parse Rom Log File	Activate the Parse ROM Log File option and specify the information that the debugger needs in order to show detailed stack information, set breakpoints, and show source level debugging information for ROM images.
Symbian Rom Log File	In the Symbian Rom Log File text field, browse to or enter the full path and name of the log file that corresponds to the ROM image on the target device. This log file is generated by default when the ROM image is built.
Symbian Epoc32 Directory	Specifies the epoc32 directory in which the ROM image and log files are stored. Since the log file may not contain full paths to the ROM components on the host PC, you need to enter this epoc32 directory. + NOTE Always include the epoc32 folder in this path.
Log unresolved modules	Activate the Log unresolved modules option to have the debugger output a list of components from the specified ROMBUILD log file that do not have debugger symbolic information. The list is displayed in the debugger console window at the beginning of the debug session. + NOTE You cannot perform source-level debugging on components that do not include symbolic information.

Item	Explanation
Qt Versions	Shows a list of installed Qt versions installed and available for Qt projects.
Add...	Click Add to open the Add new Qt version dialog where you can specify a Qt SDK by name and location. - - Figure 2. Add new Qt version dialog
Edit...	Click Edit to open the Edit Qt Version dialog where you can modify the Qt SDK information for the selected Qt version. - - Figure 3. Edit Qt Version dialog
Remove	Click Remove to delete the selected Qt SDK from the Qt version list.
Default	Click Default to identify the selected Qt SDK as the default SDK to use for Qt projects.
Auto update QMAKESPEC when applying changes	Enable to automatically update QMAKESPEC when any changes are made to a Qt version. The default setting is enabled.
Auto update make command when applying changes	Enable to automatically update make when any changes are made to a Qt version. The default setting is enabled.

Item	Explanation
Qt Versions	Shows a list of installed Qt versions installed and available for Qt projects.
Add...	Click Add to open the Add new Qt version dialog where you can specify a Qt SDK by name and location. + + Figure 2. Add new Qt version dialog
Edit...	Click Edit to open the Edit Qt Version dialog where you can modify the Qt SDK information for the selected Qt version. + + Figure 3. Edit Qt Version dialog
Remove	Click Remove to delete the selected Qt SDK from the Qt version list.
Default	Click Default to identify the selected Qt SDK as the default SDK to use for Qt projects.
Auto update QMAKESPEC when applying changes	Enable to automatically update QMAKESPEC when any changes are made to a Qt version. The default setting is enabled.
Auto update make command when applying changes	Enable to automatically update make when any changes are made to a Qt version. The default setting is enabled.

Item	Explanation
Use Qt version	Select the Qt version to associate with this project. Choose Default to always use the default Qt version as set in the Qt preference panel or select from any Qt version listed.
Run qmake when .pro file changes	Enable to keep the Carbide project and .pro file in sync during development. Qmake will be invoked whenever the .pro file changes so that the bld.inf and .mmp file will always be in sync. The default setting is enabled.

Item	Explanation
Use Qt version	Select the Qt version to associate with this project. Choose Default to always use the default Qt version as set in the Qt preference panel or select from any Qt version listed.
Run qmake when .pro file changes	Enable to keep the Carbide project and .pro file in sync during development. Qmake will be invoked whenever the .pro file changes so that the bld.inf and .mmp file will always be in sync. The default setting is enabled.

Item	Explanation
Target File	Specifies the filename of the compiled AIF file, relative to the target path. Click the untitled.aif button to set the target file based on the SDK and project name.
Resource File Path	Choose a resource file from the current project, browse the file system or enter the path. For relative paths use the Carbide project as the reference point, not the MMP file location.
Up	Select an image in the list and click Up to move the selection one position up in the list.
Down	Select an image in the list and click Down to move the selection one position down in the list.
Pair Image and Mask	Select two adjacent unpaired BMP image entries in the list and click this button to combine the images together into image/mask pairs.
Split Image and Mask	Select a paired BMP image in the list and click this button to split the image into image and mask entries.
Swap Image and Mask	Select a paired BMP image in the list and click this button to swap the image and mask files and format information in paired image entries.
Add From Project	Click this button to open an Add Images from Project dialog to reference available images in the project.
Add From Filesystem	Click this button to open an Add Images From Filesystem dialog to locate and reference existing images in the filesystem or copy images to the project.
Remove	Select an image and click Remove to remove image entry from the list. This does not delete file from directory.
Color depth	Select the bit depth used to encode the image at build time.
Mask depth	Select the bit depth used to encode the mask at build time. Options include: - - n/a - Do not apply mask depth to images - 1 - A 1-bit mask treats pixels as "on/off" bits, where black is opaque and white is transparent. - 8 - An 8-bit mask is treated as alpha values, where black is transparent and white is opaque. -
Color format	Select Color to encode the image(s) as color or select Grayscale to encode the image(s) as grayscale.
Preview	A preview of the image as it will appear at runtime.

Item	Explanation
Target File	Specifies the filename of the compiled AIF file, relative to the target path. Click the untitled.aif button to set the target file based on the SDK and project name.
Resource File Path	Choose a resource file from the current project, browse the file system or enter the path. For relative paths use the Carbide project as the reference point, not the MMP file location.
Up	Select an image in the list and click Up to move the selection one position up in the list.
Down	Select an image in the list and click Down to move the selection one position down in the list.
Pair Image and Mask	Select two adjacent unpaired BMP image entries in the list and click this button to combine the images together into image/mask pairs.
Split Image and Mask	Select a paired BMP image in the list and click this button to split the image into image and mask entries.
Swap Image and Mask	Select a paired BMP image in the list and click this button to swap the image and mask files and format information in paired image entries.
Add From Project	Click this button to open an Add Images from Project dialog to reference available images in the project.
Add From Filesystem	Click this button to open an Add Images From Filesystem dialog to locate and reference existing images in the filesystem or copy images to the project.
Remove	Select an image and click Remove to remove image entry from the list. This does not delete file from directory.
Color depth	Select the bit depth used to encode the image at build time.
Mask depth	Select the bit depth used to encode the mask at build time. Options include: + + n/a - Do not apply mask depth to images + 1 - A 1-bit mask treats pixels as "on/off" bits, where black is opaque and white is transparent. + 8 - An 8-bit mask is treated as alpha values, where black is transparent and white is opaque. +
Color format	Select Color to encode the image(s) as color or select Grayscale to encode the image(s) as grayscale.
Preview	A preview of the image as it will appear at runtime.

Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
+ \ No newline at end of file diff -r b0d232312e83 -r a546534a48de core/com.nokia.carbide.cpp.doc.user/html/reference/search/view_system_search.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/search/view_system_search.htm Thu Apr 15 18:07:10 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/search/view_system_search.htm Fri Apr 16 09:51:37 2010 -0500 @@ -1,81 +1,81 @@ - - - - - - -System Search view - - - -

System Search view

The System Search view displays the results of a search based on the criteria used in the System Search page. This view (Figure 1) appears automatically when a directory search is performed. You can also open it using the Window > Show View > Other... option where it is found in the Show View dialog under the System Search category.

Figure 1. System Search view after a system search

The System Search view displays these columns:

Name — name of the matched file and the number of matches found within it
Type — the file type extension (.c, .c++, etc.)
Size — size of the file in bytes
Date Modified — last date the file was modified
Path — complete path to locate the file

These columns are sortable, simply click the column title to sort in ascending or descending order. Most reordering is based on strings and will be instant, but sorting by Size may take longer depending upon how many file matches have been made.

System Search view toolbar icons

The table below lists the icons displayed in the System Search view toolbar.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Icon	Item	Explanation
	Show Next Match	Opens the file in an editor if not already open and shows the first match in the file. If an editor is already open then show the next match in the file.
	Show Previous Match	Opens the file in an editor if not already open and shows the last match in the file. If an editor is already open then show the previous match in the file.
	Remove Selected Matches	Removes the currently selected files from the search list.
	Remove All Matches	Removes all files from the search list.
	Run the Current Search Again	Repeat the search using the same criteria.
	Cancel Current Search	Click to cancel the current search in progress.
	Show Previous Searches	Shows a menu with the 10 previous searches. Select a search to show its results in the view. Select History to manage the list of all previous searches or change the number of histories you can save. Choose Clear History to delete the stored searches.
	Pin the Search View	Toggles the pin state of the System Search view.
	Menu	Set filters for the view or open the System Search preference panel.

- - - - + + + + + + +System Search view + + + +

System Search view

Figure 1. System Search view after a system search

The System Search view displays these columns:

Name — name of the matched file and the number of matches found within it
Type — the file type extension (.c, .c++, etc.)
Size — size of the file in bytes
Date Modified — last date the file was modified
Path — complete path to locate the file

System Search view toolbar icons

The table below lists the icons displayed in the System Search view toolbar.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Icon	Item	Explanation
	Show Next Match	Opens the file in an editor if not already open and shows the first match in the file. If an editor is already open then show the next match in the file.
	Show Previous Match	Opens the file in an editor if not already open and shows the last match in the file. If an editor is already open then show the previous match in the file.
	Remove Selected Matches	Removes the currently selected files from the search list.
	Remove All Matches	Removes all files from the search list.
	Run the Current Search Again	Repeat the search using the same criteria.
	Cancel Current Search	Click to cancel the current search in progress.
	Show Previous Searches	Shows a menu with the 10 previous searches. Select a search to show its results in the view. Select History to manage the list of all previous searches or change the number of histories you can save. Choose Clear History to delete the stored searches.
	Pin the Search View	Toggles the pin state of the System Search view.
	Menu	Set filters for the view or open the System Search preference panel.

+ + + + diff -r b0d232312e83 -r a546534a48de core/com.nokia.carbide.cpp.doc.user/html/reference/search/wnd_system_search.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/search/wnd_system_search.htm Thu Apr 15 18:07:10 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/search/wnd_system_search.htm Fri Apr 16 09:51:37 2010 -0500 @@ -1,60 +1,60 @@ - - - - - - -System Search - - - -

System Search

Use the System Search page of the Search window to perform a textual search of files by directory, on your hard drive. This enables you to search for files inside directories located outside of the project workspace. In addition, there are additional search choices including:

File Search - does a textual search of files in the workspace. This search comes from the Eclipse platform.
C/C++ Search - searches via the C++ index, not a simple textual search. This search comes from CDT.

Choose Search > System Search to open the Search window and perform a directory defined textual search. The results are then shown in the System Search view. Some of the search behaviors and apperance are controlled by settings in the System Search preference panel.

Figure 1. System Search page in the Search window

Table 1. System Search page options

- - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Search string	Enter text into the Search string text box to search for specific strings within files. Leave empty if you are only looking for files by name and not content. You can control how the text is interpreted using these options: - - Case sensitive — enable to make the search case sensitive - Regular expression — enable to use regular expression in the Search string text box -
File name patterns	Enter the file types to search for seperated by commas, or click Choose to select file types in the preset list in the Select Types dialog.
Folder	Enter text into the Folder text box or click Browse to search to search a specific folder. You can control how the folder search is conducted using these options: - - Search subfolders — enable to recusively search subfolders in the selected folder for matching files - Search hidden files — enable to also search the folder/subfolders hidden files -
Customize...	Specify which search tabs should appear in the Search window. - NOTE Use the Window > Customize Perspective > Commands page to hide specific commands you never use.

Other references

Search view
Search actions

- - - - + + + + + + +System Search + + + +

System Search

File Search - does a textual search of files in the workspace. This search comes from the Eclipse platform.
C/C++ Search - searches via the C++ index, not a simple textual search. This search comes from CDT.

Figure 1. System Search page in the Search window

Table 1. System Search page options

+ + + + + + + + + + + + + + + + + + + + + +

Item	Explanation
Search string	Enter text into the Search string text box to search for specific strings within files. Leave empty if you are only looking for files by name and not content. You can control how the text is interpreted using these options: + + Case sensitive — enable to make the search case sensitive + Regular expression — enable to use regular expression in the Search string text box +
File name patterns	Enter the file types to search for seperated by commas, or click Choose to select file types in the preset list in the Select Types dialog.
Folder	Enter text into the Folder text box or click Browse to search to search a specific folder. You can control how the folder search is conducted using these options: + + Search subfolders — enable to recusively search subfolders in the selected folder for matching files + Search hidden files — enable to also search the folder/subfolders hidden files +
Customize...	Specify which search tabs should appear in the Search window. + NOTE Use the Window > Customize Perspective > Commands page to hide specific commands you never use.

Other references

Search view
Search actions

+ + + + diff -r b0d232312e83 -r a546534a48de core/com.nokia.carbide.cpp.doc.user/html/reference/search/wnd_system_search_prefs.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/search/wnd_system_search_prefs.htm Thu Apr 15 18:07:10 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/search/wnd_system_search_prefs.htm Fri Apr 16 09:51:37 2010 -0500 @@ -1,49 +1,49 @@ - - - - - - -System Search preferences - - - -

System Search preferences

Use the System Search preference panel to control System Search behaviors. Choose Window > Preferences > System Search to open the System Search preference panel.

Figure 1. System Search preference panel

Table 1. System Search page options

- - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Reuse editors to show matches	Enable this option to keep using the same editor for search results to reduce the number of open editors.
Ignore potential matches	Enable this option if you only want to see exact matches.
Emphasize potential matches	Enable this option to highlight potential matches in the System Search view. If the search engine isn't 100% sure about the match then it is considered a potential match.
Foreground color for potential matches	Enable this option to select the foreground color for potential matches.
Default perspective for the Search view	This option allows you to define which perspective should be brought to the front when there are new search results.

Other references

System Search page

- - - - + + + + + + +System Search preferences + + + +

System Search preferences

Use the System Search preference panel to control System Search behaviors. Choose Window > Preferences > System Search to open the System Search preference panel.

Figure 1. System Search preference panel

Table 1. System Search page options

+ + + + + + + + + + + + + + + + + + + + + + + + + +

Item	Explanation
Reuse editors to show matches	Enable this option to keep using the same editor for search results to reduce the number of open editors.
Ignore potential matches	Enable this option if you only want to see exact matches.
Emphasize potential matches	Enable this option to highlight potential matches in the System Search view. If the search engine isn't 100% sure about the match then it is considered a potential match.
Foreground color for potential matches	Enable this option to select the foreground color for potential matches.
Default perspective for the Search view	This option allows you to define which perspective should be brought to the front when there are new search results.

Other references

System Search page

+ + + + diff -r b0d232312e83 -r a546534a48de core/com.nokia.carbide.cpp.doc.user/html/reference/trk/exporting_remote_conns.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/exporting_remote_conns.htm Thu Apr 15 18:07:10 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/exporting_remote_conns.htm Fri Apr 16 09:51:37 2010 -0500 @@ -1,37 +1,37 @@ - - - - - - -Exporting Remote Connections - - - - -

Exporting Remote Connections

You can export remote connection settings for sharing and import settings created by others using the Import/Export commands.

Exporting Remote Connections
Importing Remote Connections

To export one or more remote connections:

Click the File > Export... menu option.
Select the Remote Connections > Remote Connections Data wizard in the Select page (Figure 1), then click Next.

Figure 1. Select page showing Remote Connections Data wizard

Choose file and remote connections to export (Figure 2) in the Export Remote Connections Data page.

Figure 2. Enable remote connections to export to chosen file

Click Finish to save the selected remote connections to the file.

Related references

On-Device Setup
Install latest TRK

- - - + + + + + + +Exporting Remote Connections + + + + +

Exporting Remote Connections

You can export remote connection settings for sharing and import settings created by others using the Import/Export commands.

Exporting Remote Connections
Importing Remote Connections

To export one or more remote connections:

Click the File > Export... menu option.
Select the Remote Connections > Remote Connections Data wizard in the Select page (Figure 1), then click Next.

Figure 1. Select page showing Remote Connections Data wizard

Choose file and remote connections to export (Figure 2) in the Export Remote Connections Data page.

Figure 2. Enable remote connections to export to chosen file

Click Finish to save the selected remote connections to the file.

Related references

On-Device Setup
Install latest TRK

+ + + diff -r b0d232312e83 -r a546534a48de core/com.nokia.carbide.cpp.doc.user/html/reference/trk/importing_remote_conns.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/importing_remote_conns.htm Thu Apr 15 18:07:10 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/importing_remote_conns.htm Fri Apr 16 09:51:37 2010 -0500 @@ -1,37 +1,37 @@ - - - - - - -Importing Remote Connections - - - - -

Importing Remote Connections

You can export remote connection settings for sharing and import settings created by others using the Import/Export commands.

Exporting Remote Connections
Importing Remote Connections

To import one or more remote connections:

Click the File > Import... menu option.
Select the Remote Connections > Remote Connections Data wizard in the Select page (Figure 1), then click Next.

Figure 1. Select page showing Remote Connections Data wizard

Choose file and remote connections to export (Figure 2) in the Import Remote Connections Data page.

Figure 2. Enable remote connections to import

Click Finish to import the selected remote connections into Carbide.

Related references

On-Device Setup
Install latest TRK

- - - + + + + + + +Importing Remote Connections + + + + +

Importing Remote Connections

You can export remote connection settings for sharing and import settings created by others using the Import/Export commands.

Exporting Remote Connections
Importing Remote Connections

To import one or more remote connections:

Click the File > Import... menu option.
Select the Remote Connections > Remote Connections Data wizard in the Select page (Figure 1), then click Next.

Figure 1. Select page showing Remote Connections Data wizard

Choose file and remote connections to export (Figure 2) in the Import Remote Connections Data page.

Figure 2. Enable remote connections to import

Click Finish to import the selected remote connections into Carbide.

Related references

On-Device Setup
Install latest TRK

+ + + diff -r b0d232312e83 -r a546534a48de core/com.nokia.carbide.cpp.doc.user/html/reference/trk/panel_filter.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/panel_filter.htm Thu Apr 15 18:07:10 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/panel_filter.htm Fri Apr 16 09:51:37 2010 -0500 @@ -4,14 +4,14 @@ -Filter Preferences +Launch Configurations -

Launch Configuration Filters

The Launch Configuration Filters Preference window provides additional options for filtering out the launch configurations that appear in the list of configurations.

Launch Configurations

The Launch Configuration preference panel provides additional options for filtering out the launch configurations that appear in the list of configurations.

To access the Launch Configurations Filter Window

To access the Launch Configurations preference panel

Select the Run > Debug As menu item
Expand the Run/Debug group
Expand Launching and select Launch Configurations

Figure 2 - Launch Configurations Filter

Use the New Connection wizard to verify and update Carbide software services on a device. Click the Help > On-Device Connections... menu option to open. Current services available include TRK, Tracing, and others. The following tabs are present:

Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
+ \ No newline at end of file diff -r b0d232312e83 -r a546534a48de core/com.nokia.carbide.cpp.doc.user/html/reference/view_cpp_projects.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_cpp_projects.htm Thu Apr 15 18:07:10 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_cpp_projects.htm Fri Apr 16 09:51:37 2010 -0500 @@ -1,39 +1,39 @@ - - - - - - -Project Explorer View - - - -

Project Explorer View

The Project Explorer view (Figure 1) displays relevant C/C++ projects located in the current workspace using a tree structure. Use this view to manage all the projects located in the workspace. The view is customizable and takes advantage of working sets.

The content of a project is dependent upon how it was created in the workspace.

Figure 1 - Project Explorer view showing projects in the current workspace

The directories that appear in the project include:

sis—the storage location for the final output files. The output file is linked from the top level of the project with a file of the same name. Both the binary and link files can be expanded to show the source files used to build the program.
Includes—a listing of all the include files used to build the project.
Executables - a listing of debuggable executables imported into the Executables view
User specified—many other directories like src, inc, data, and others are used to store specific types of project files. The names used for the directories are defined in the Project Directories page when the project is created.

-
NOTE Only the directories specified by the mmp file are created during import.
-

The files that appear in the project directories can be either:

files ()—these files are located in the workspace within the project directories. Double-click a file icon to open it for editing.
folder links—these are links pointing to folders that enable the project to support cvs related sources.

See C/C++ Development User Guide > Reference > C/C++ Views and Editors > Project Explorer view for more info.

Related references

Carbide C/C++ Perspective

- - - + + + + + + +Project Explorer View + + + +

Project Explorer View

The content of a project is dependent upon how it was created in the workspace.

Figure 1 - Project Explorer view showing projects in the current workspace

The directories that appear in the project include:

sis—the storage location for the final output files. The output file is linked from the top level of the project with a file of the same name. Both the binary and link files can be expanded to show the source files used to build the program.
Includes—a listing of all the include files used to build the project.
Executables - a listing of debuggable executables imported into the Executables view
User specified—many other directories like src, inc, data, and others are used to store specific types of project files. The names used for the directories are defined in the Project Directories page when the project is created.

+
NOTE Only the directories specified by the mmp file are created during import.
+

The files that appear in the project directories can be either:

files ()—these files are located in the workspace within the project directories. Double-click a file icon to open it for editing.
folder links—these are links pointing to folders that enable the project to support cvs related sources.

See C/C++ Development User Guide > Reference > C/C++ Views and Editors > Project Explorer view for more info.

Related references

Carbide C/C++ Perspective

+ + + \ No newline at end of file diff -r b0d232312e83 -r a546534a48de core/com.nokia.carbide.cpp.doc.user/html/reference/view_executables.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_executables.htm Thu Apr 15 18:07:10 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_executables.htm Fri Apr 16 09:51:37 2010 -0500 @@ -97,7 +97,7 @@

Debug perspective

- + diff -r b0d232312e83 -r a546534a48de core/com.nokia.carbide.cpp.doc.user/html/reference/view_log.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_log.htm Thu Apr 15 18:07:10 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_log.htm Fri Apr 16 09:51:37 2010 -0500 @@ -66,7 +66,7 @@

- + diff -r b0d232312e83 -r a546534a48de core/com.nokia.carbide.cpp.doc.user/html/reference/view_module_wnd.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_module_wnd.htm Thu Apr 15 18:07:10 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_module_wnd.htm Fri Apr 16 09:51:37 2010 -0500 @@ -18,7 +18,7 @@

Debug view

- + diff -r b0d232312e83 -r a546534a48de core/com.nokia.carbide.cpp.doc.user/html/reference/view_reg_details.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_reg_details.htm Thu Apr 15 18:07:10 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_reg_details.htm Fri Apr 16 09:51:37 2010 -0500 @@ -1,138 +1,138 @@ - - - - - - -Registers Details Window - - - -

Registers Details Window

The Register Details window (Windows OS) lets you view detailed information about individual bits of registers from 2 bits to 32 bits in size. This window shows information for both system registers and memory-mapped registers. To open the Register Details window, click View > Register Details or Window > Register Details Window.

The Register Details window has fields that describe the register, its bitfields, and the values of those bitfields. XML files in the Registers folder of your Carbide installation provide the information that appears in the window. The Registers folder is inside the Support folder. The Support folder is inside the Plugins folder of your Carbide installation.

Figure 1 shows the Register Details window. Table 1 explains items in the window.

Figure 1 Register Details window
-

Table 1. Register Details window—items

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Icon	Explanation
Description File text box		Enter the name or full path to the XML file for the register you want to view, or click the Browse button to open a dialog box that you can use to specify the file.
Register Name		Shows the name of the register depicted in the window.
Address text box		Enter the starting address of the register values that you want to see in the Register Display. - An error message appears if you enter an invalid starting address.
Format list box		Specify the data format for bit values in the Register Display: - - Binary - Character - Decimal - Unsigned Decimal - Hexadeccimal - Default—have the IDE determine the best format -
Register Display		Shows a depiction of the register that you specify in the Description File text box, including individual register bits and their values.
Bitfield Name list box		Specify a bitfield to highlight in the Register Display. The Description portion of the window reflects available information for the bitfield. - Select None to have the Description portion of the window reflect information for the entire register and not a bitfield in that register.
Bit Value text box		Shows the current value of the bits in the Bitfield Name list box, according to the format that you specify in the Format list box. - Click the spin buttons to increment or decrement the current value, or enter a new value in the text box. - Changing the value changes only the Register Display. You must click the Write button to write the new value to the register itself.
Bit Value Modifier list box		Specify a new value for the selected bitfield, or view a brief explanation of specific bitfield values. - Changing the value changes only the Register Display. You must click the Write button to write the new value to the register.
Description		Shows a description of the register or a selected bitfield in the register. - Use the Description File text box to specify the register. - Use the Text View list box to view specific register information, such as register descriptions, bitfield descriptions, and register details.
Revert button		Click to change a modified value in the Register Display to its original value. - If you clicked the Write button to write a new value to the register, you cannot revert that value.
Read button		Click to have the Register Display reflect current bit values from the register itself.
Write button		Click to write the bit values in the Register Display to the register. - After you write new values to the register, you cannot revert them.
Reset Value button		Click to restore the default value for the selected bitfield. - The IDE disables this button if the selected bitfield does not have a default value.
Text View list box		Use to specify information that appears in the Description portion of the window.

Description File

Enter in this text box the name of the register that you want to see in the Register Display of the Register Details window. Alternatively, enter the full path to the register description file on your computer, or click the Browse button to open a dialog box that lets you specify the register description file. The text box is not case sensitive.

After you enter a name or path, the debugger searches for a matching register description file in the Registers folder of your Carbide installation and the project access paths. If the debugger finds a matching file, the Register Display updates the information in the Register Details window. If the debugger does not find a matching name, an error message appears.

For example, to view the contents of the Opcode register, you can:

type Opcode in the Description File text box and press Enter or Return, or
type the full path to the opcode.xml file in the Registers folder and press Enter or Return.

The debugger matches your entry with the opcode.xml file in the Registers folder. The Register Display in the Register Details window updates its information to show Opcode register details.

The debugger also updates the Register Display to show the current values in the register. If the debugger fails to update the display, an error message appears.

Register Display

This display shows the current contents of 32 bits of register data, starting at the address that you specify in the Address text box. The data appears according to the format that you specify in the Format list box.

The Register Display groups the 32 bits of data into register bitfields. Clicking one of the bits selects its associated bitfield. Additional information about the bitfield, such as its name and permissions, appears in the Description portion of the Register Details window.

Text View

Use this list box to change the information that appears in the Description portion of the Register Details window:

Auto—select to have the IDE determine which information to display in the window
Register Description—select to show information about the entire register, such as the name of the register itself and the meaning of its contents
Bitfield Description—select to show information about the selected bitfield in the Register Display, such as the name of the bitfield and its access permissions
Register Details—select to show in-depth information about the current register, such as its name, its bit values, and bit-value explanations
-

- - - + + + + + + +Registers Details Window + + + +

Registers Details Window

Figure 1 shows the Register Details window. Table 1 explains items in the window.

Figure 1 Register Details window
+

Table 1. Register Details window—items

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Item	Icon	Explanation
Description File text box		Enter the name or full path to the XML file for the register you want to view, or click the Browse button to open a dialog box that you can use to specify the file.
Register Name		Shows the name of the register depicted in the window.
Address text box		Enter the starting address of the register values that you want to see in the Register Display. + An error message appears if you enter an invalid starting address.
Format list box		Specify the data format for bit values in the Register Display: + + Binary + Character + Decimal + Unsigned Decimal + Hexadeccimal + Default—have the IDE determine the best format +
Register Display		Shows a depiction of the register that you specify in the Description File text box, including individual register bits and their values.
Bitfield Name list box		Specify a bitfield to highlight in the Register Display. The Description portion of the window reflects available information for the bitfield. + Select None to have the Description portion of the window reflect information for the entire register and not a bitfield in that register.
Bit Value text box		Shows the current value of the bits in the Bitfield Name list box, according to the format that you specify in the Format list box. + Click the spin buttons to increment or decrement the current value, or enter a new value in the text box. + Changing the value changes only the Register Display. You must click the Write button to write the new value to the register itself.
Bit Value Modifier list box		Specify a new value for the selected bitfield, or view a brief explanation of specific bitfield values. + Changing the value changes only the Register Display. You must click the Write button to write the new value to the register.
Description		Shows a description of the register or a selected bitfield in the register. + Use the Description File text box to specify the register. + Use the Text View list box to view specific register information, such as register descriptions, bitfield descriptions, and register details.
Revert button		Click to change a modified value in the Register Display to its original value. + If you clicked the Write button to write a new value to the register, you cannot revert that value.
Read button		Click to have the Register Display reflect current bit values from the register itself.
Write button		Click to write the bit values in the Register Display to the register. + After you write new values to the register, you cannot revert them.
Reset Value button		Click to restore the default value for the selected bitfield. + The IDE disables this button if the selected bitfield does not have a default value.
Text View list box		Use to specify information that appears in the Description portion of the window.

Description File

For example, to view the contents of the Opcode register, you can:

type Opcode in the Description File text box and press Enter or Return, or
type the full path to the opcode.xml file in the Registers folder and press Enter or Return.

The debugger matches your entry with the opcode.xml file in the Registers folder. The Register Display in the Register Details window updates its information to show Opcode register details.

The debugger also updates the Register Display to show the current values in the register. If the debugger fails to update the display, an error message appears.

Register Display

Text View

Use this list box to change the information that appears in the Description portion of the Register Details window:

Auto—select to have the IDE determine which information to display in the window
Register Description—select to show information about the entire register, such as the name of the register itself and the meaning of its contents
Bitfield Description—select to show information about the selected bitfield in the Register Display, such as the name of the bitfield and its access permissions
Register Details—select to show in-depth information about the current register, such as its name, its bit values, and bit-value explanations
+

+ + + \ No newline at end of file diff -r b0d232312e83 -r a546534a48de core/com.nokia.carbide.cpp.doc.user/html/reference/view_sym_proj_nav.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_sym_proj_nav.htm Thu Apr 15 18:07:10 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_sym_proj_nav.htm Fri Apr 16 09:51:37 2010 -0500 @@ -46,7 +46,7 @@

- + diff -r b0d232312e83 -r a546534a48de core/com.nokia.carbide.cpp.doc.user/html/reference/view_variables.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_variables.htm Thu Apr 15 18:07:10 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_variables.htm Fri Apr 16 09:51:37 2010 -0500 @@ -1,86 +1,85 @@ - - - - - - -Variables View - - - -

Variables View

The Variables view allows manipulation of the variables or variable hierarchy used in source code. For example, you can change the variable format, change a variables value, add watchpoints, and add global variables.

Figure 1 shows the Variables view with Show Type Names option enabled.

Figure 1 - Variables view showing type names

Table 1. Variables view—items

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Icons	Explanation
Show Type Names		Toggles the display of type names in the Variables view.
Show Logical Structure		Not available in C/C++ yet.
Collapse All		Collapses all expanded variables into the top level.
Add Global Variables		Click to open a window where you can select one or more global variables to display in the Variables view. Global variables appear at the top of the variables list.
Remove Selected Global Variables		Click to remove all currently selected global variables from the variables list.
Remove All Global Variables		Click to remove all global variables from the variables list.
Menu		Enables you to modifiy the Layout to change the view orientation between: horizontal, vertical, or variables pane only. - In addition, use Show All Variables to toggle between showing only those variables that are in scope and live or show all local variables, even if redundant. With this option on you will see all of the variables including the multiple defined variables like “i” for your loops and ones that may no longer have accurate values.

To open the Variables view

Click Window > Show View > Variables

The Variables view appears.

Related concepts

Related tasks

Related References

Expressions View
Variables View

- - - - + + + + + + +Variables View + + + +

Variables View

Figure 1 shows the Variables view with Show Type Names option enabled.

Figure 1 - Variables view showing type names

Table 1. Variables view—items

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Item	Icons	Explanation
Show Type Names		Toggles the display of type names in the Variables view.
Show Logical Structure		Not available in C/C++ yet.
Collapse All		Collapses all expanded variables into the top level.
Add Global Variables		Click to open a window where you can select one or more global variables to display in the Variables view. Global variables appear at the top of the variables list.
Remove Selected Global Variables		Click to remove all currently selected global variables from the variables list.
Remove All Global Variables		Click to remove all global variables from the variables list.
Menu		Enables you to modifiy the Layout to change the view orientation between: horizontal, vertical, or variables pane only. + In addition, use Show All Variables to toggle between showing only those variables that are in scope and live or show all local variables, even if redundant. With this option on you will see all of the variables including the multiple defined variables like “i” for your loops and ones that may no longer have accurate values.

To open the Variables view

Click Window > Show View > Variables

The Variables view appears.

Related concepts

Related tasks

Related References

Expressions View

+ + + + diff -r b0d232312e83 -r a546534a48de core/com.nokia.carbide.cpp.doc.user/html/reference/views.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/views.htm Thu Apr 15 18:07:10 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/views.htm Fri Apr 16 09:51:37 2010 -0500 @@ -1,20 +1,20 @@ - - - - - - -Working with Memory - - - -

Working with Memory

This section explains how to work with variables in a Carbide.c++ debugging session. The following views show various types of information about variables:

Memory view —shows the memory that your project manipulates as it executes
Registers view—shows the register contents of a processor

- - - - + + + + + + +Working with Memory + + + +

Working with Memory

This section explains how to work with variables in a Carbide.c++ debugging session. The following views show various types of information about variables:

Memory view —shows the memory that your project manipulates as it executes
Registers view—shows the register contents of a processor

+ + + + diff -r b0d232312e83 -r a546534a48de core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_carbide_pref_x86.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_carbide_pref_x86.htm Thu Apr 15 18:07:10 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_carbide_pref_x86.htm Fri Apr 16 09:51:37 2010 -0500 @@ -1,25 +1,25 @@ - - - - - - -Unsetting Built-in Environment - - - -

Unsetting Built-in Environment

The Carbide.c++ > Build page in the Preferences window provides an option to use the local x86 build tools for each emulator build. A directory named x86Build at the root of the product installation contains the build tools, libraries, and env_update.exe file.

Uncheck the "Use built-in Nokia x86 environment variables for WINSCW builds" option if you do not want to use the built-in compiler.

Figure 1 shows the Build preferences window.

Figure 1 -Build preferences window showing Emulator Build Options

Related references

- - - - + + + + + + +Unsetting Built-in Environment + + + +

Unsetting Built-in Environment

Uncheck the "Use built-in Nokia x86 environment variables for WINSCW builds" option if you do not want to use the built-in compiler.

Figure 1 shows the Build preferences window.

Figure 1 -Build preferences window showing Emulator Build Options

Related references

+ + + + diff -r b0d232312e83 -r a546534a48de core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_debugger_prefs.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_debugger_prefs.htm Thu Apr 15 18:07:10 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_debugger_prefs.htm Fri Apr 16 09:51:37 2010 -0500 @@ -1,60 +1,60 @@ - - - - - - -Carbide.c++ Debugger Preferences - - - - -

Carbide.c++ Debugger preferences

The Debug > -Carbide.c++ Debugger preference panel provides global debugger settings for the Carbide.c++ tools.

Figure 1 - Carbide.c++ Debugger preference panel

Table 1. Carbide.c++ Debugger panel—items

- - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Attempt to show the dynamic runtime type of objects	Enable this option to have the debugger deduce the actual type of an object at runtime and display it in the Variables view (applies to x86 only). By default, the debugger does not attempt to determine the type of an object at runtime and will simply show its declared type. Enabling this option can slow the start of a debug session.
Do not step into runtime support code	Select this option to avoid stepping into runtime support code. Runtime support code is generated by the compiler to support C++ features like new and delete. When enabled the debugger attempts to identify and skip this glue code and step directly into your code. If this option is disabled the debugger steps into this language support code. For example if you are debugging this line of code and step in: - MyClass* var = new MyClass(); - With this option selected the debugger will skip the code that implements the operator new and step into the constructor for MyClass. If this option is disabled the debugger would step into the code in new that allocates the object.
Default size for unbounded arrays	Enter the number of array objects to display by default.
Find source files outside the SDK	Enable to have the debugger automatically search for source files outside of the SDK. If disabled, the debugger will only look within the SDK epocroot directory.
Time interval for auto-refreshing OS View	Determines how often to refresh data in the Symbian OS Data view which is available to the developer when using TRK or stop-mode debugging.

To access the Carbide.c++ Debugger Preferences

Select the Window > Preferences menu item
-
The Preferences window (Figure 1) appears.
Expand the C/C++ and Debug sections
Select the Carbide.c++ Debugger item
-
The Carbide.c++ Debugger preference panel appears.
-

- - - + + + + + + +Carbide.c++ Debugger Preferences + + + + +

Carbide.c++ Debugger preferences

The Debug > +Carbide.c++ Debugger preference panel provides global debugger settings for the Carbide.c++ tools.

Figure 1 - Carbide.c++ Debugger preference panel

Table 1. Carbide.c++ Debugger panel—items

+ + + + + + + + + + + + + + + + + + + + + + + + + +

Item	Explanation
Attempt to show the dynamic runtime type of objects	Enable this option to have the debugger deduce the actual type of an object at runtime and display it in the Variables view (applies to x86 only). By default, the debugger does not attempt to determine the type of an object at runtime and will simply show its declared type. Enabling this option can slow the start of a debug session.
Do not step into runtime support code	Select this option to avoid stepping into runtime support code. Runtime support code is generated by the compiler to support C++ features like new and delete. When enabled the debugger attempts to identify and skip this glue code and step directly into your code. If this option is disabled the debugger steps into this language support code. For example if you are debugging this line of code and step in: + MyClass* var = new MyClass(); + With this option selected the debugger will skip the code that implements the operator new and step into the constructor for MyClass. If this option is disabled the debugger would step into the code in new that allocates the object.
Default size for unbounded arrays	Enter the number of array objects to display by default.
Find source files outside the SDK	Enable to have the debugger automatically search for source files outside of the SDK. If disabled, the debugger will only look within the SDK epocroot directory.
Time interval for auto-refreshing OS View	Determines how often to refresh data in the Symbian OS Data view which is available to the developer when using TRK or stop-mode debugging.

To access the Carbide.c++ Debugger Preferences

Select the Window > Preferences menu item
+
The Preferences window (Figure 1) appears.
Expand the C/C++ and Debug sections
Select the Carbide.c++ Debugger item
+
The Carbide.c++ Debugger preference panel appears.
+

+ + + \ No newline at end of file diff -r b0d232312e83 -r a546534a48de core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_diagnostic_logs_pref.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_diagnostic_logs_pref.htm Thu Apr 15 18:07:10 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_diagnostic_logs_pref.htm Fri Apr 16 09:51:37 2010 -0500 @@ -34,7 +34,7 @@

Carbide Project Settings

- + diff -r b0d232312e83 -r a546534a48de core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_import_bitmaps.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_import_bitmaps.htm Thu Apr 15 18:07:10 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_import_bitmaps.htm Fri Apr 16 09:51:37 2010 -0500 @@ -1,58 +1,58 @@ - - - - - - -Import Bitmaps - - - -

Import Bitmaps

Use the Import window to import bitmap resources from the file system.

Figure 1 - Import Bitmaps window

Table 1. Import Bitmaps window—items

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
From directory	Path to folder containing bitmaps files to import. Click Browse to choose a different location.
Filter Types...	Click to open a dialog and select filter options.
Select All	Click to select all files.
Deselect All	Click to deselect all files.
Into folder	Specify the location within the project to store the imported files.
Overwrite existing resources without warning	Enable to overwrite existing resources using the same names with the new ones being imported.
Create complete folder structure	Create a duplicate of the system folder structure at the project location set in the Into folder text box.
Create selected folders only	Create folder structures at the project location set in the Into folder text box only for the selected folders.

- - - + + + + + + +Import Bitmaps + + + +

Import Bitmaps

Use the Import window to import bitmap resources from the file system.

Figure 1 - Import Bitmaps window

Table 1. Import Bitmaps window—items

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Item	Explanation
From directory	Path to folder containing bitmaps files to import. Click Browse to choose a different location.
Filter Types...	Click to open a dialog and select filter options.
Select All	Click to select all files.
Deselect All	Click to deselect all files.
Into folder	Specify the location within the project to store the imported files.
Overwrite existing resources without warning	Enable to overwrite existing resources using the same names with the new ones being imported.
Create complete folder structure	Create a duplicate of the system folder structure at the project location set in the Into folder text box.
Create selected folders only	Create folder structures at the project location set in the Into folder text box only for the selected folders.

+ + + \ No newline at end of file diff -r b0d232312e83 -r a546534a48de core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_pref_code_style.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_pref_code_style.htm Thu Apr 15 18:07:10 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_pref_code_style.htm Fri Apr 16 09:51:37 2010 -0500 @@ -20,7 +20,7 @@

Setting the Workspace Code Style

Reformatting a Source File

Name	Function
- - Target name	- - Enter the name of the target file. -
- - Target type -	- - Select the type of target file from the dropdown list.
- - Target path -	- - Enter the path to the target file. -
- - UID 2 -	- UID 2 is a unique identifier number that identifies the type of interface that the project implements. The values are defined by Symbian: - - For GUI applications, it is always 0x100039CE - For static interface DLLs, the UID 2 is always 0x1000008d - For polymorphic DLLs, the UID2 is defined by the framework which is being implemented - -
- - UID 3 -	- - Application UID (or UID3) is used to uniquely identify the binary (EXE or DLL) within the system. The purpose of UID 3 is to prevent one executable from interfering the operation of another executable.
- - Project definition -	- - The Project definition group provides links to the Sources, Libraries, and Options windows. You can also select the Sources, Libraries, and Options tabs to open the related window.
- - Common tasks -	- - This group provides links to the User and System include path options located in the Options window. -

Name	Function
+ + Target name	+ + Enter the name of the target file. +
+ + Target type +	+ + Select the type of target file from the dropdown list.
+ + Target path +	+ + Enter the path to the target file. +
+ + UID 2 +	+ UID 2 is a unique identifier number that identifies the type of interface that the project implements. The values are defined by Symbian: + + For GUI applications, it is always 0x100039CE + For static interface DLLs, the UID 2 is always 0x1000008d + For polymorphic DLLs, the UID2 is defined by the framework which is being implemented + +
+ + UID 3 +	+ + Application UID (or UID3) is used to uniquely identify the binary (EXE or DLL) within the system. The purpose of UID 3 is to prevent one executable from interfering the operation of another executable.
+ + Project definition +	+ + The Project definition group provides links to the Sources, Libraries, and Options windows. You can also select the Sources, Libraries, and Options tabs to open the related window.
+ + Common tasks +	+ + This group provides links to the User and System include path options located in the Options window. +

Name	Function
- - Runtime	- - This group allows you to define various runtime options. - Capabilities - Click the Choose... button to select Capabilities. A capability is an access token that corresponds to permission to access sensitive system resources. Platform security permits access to sensitive APIs according to capabilities. Capabilities are used to specify what functionality an application is trusted to use; they are allocated to the application at build time and are policed at run time. Once the capabilities are assigned to the application, they cannot be changed. Thus an application has a set of unalterable capabilities that describe what access the application has to the APIs. - There are three suggested ways to establish which capabilities an application requires. - - The first method is initially to allocate capabilities based on the general operations that the application performs. For example, an instant messaging application would probably require NetworkServices to access the Internet and ReadUserData to read the user’s contacts. - The second method is to use the Symbian Developer Library, which lists the capabilities required by each API. Note that some APIs may be marked as “Dependent”, meaning that the need for the capability depends on the parameters being passed. For example, accessing a file in an application’s private data area requires no capabilities, but accessing a file in \sys\bin requires the AllFiles capability. - The third method is to run the application in the emulator, analyzing the debug file (in the system temporary directory) for capability violations. The output will state the API that caused the violation and what capability was expected. - - Minimum heap size - Set the heap size that you need. - Maximum heap size - Set the heap size that you need. - Stack size - Set the stack size that you need. - Process priority - Select the process priority from the dropdown list. - Secure ID - Enter the Secure ID. The SID is used to determine which private directory a process can access. It is also used to identify the caller applications. An application's SID is defined within its .mmp file, and is used to uniquely identify the application. SID values are requested from the Symbian Signed Web site (www.symbiansigned.com). The Software Installer (SWI) is responsible for ensuring that SIDs are locally unique, i.e., that no two applications have the same SID value on a particular target device. - Vendor ID - Enter the Vendor ID. This ID uniquely identifies the source of the application. If an application needs a VID, it must be certified. Noncertified applications must use a VID of 0 (KNullUid), which is the value applied by default. - Enable debugging (Symbian OS 9.4+) - Activate to enable on-device debugging for Symbian OS 9.4 and later. When activated, the DEBUGGABLE_UDEBONLY flag is added to the project .MMP file. - Paging Mode (Symbian OS 9.3+) - specify the paging mode to: not specified, paged, or unpaged.
- - Compiler Settings	- - User includes - Use the Add, Edit, and Remove buttons to add, edit, or remove the paths to the user header files used to compile source files. Use the Up and Down buttons to arrange the list of paths. - System includes - Use the Add, Edit, and Remove buttons to add, edit, or remove the paths to the system header files used to compile source files. Use the Up and Down buttons to arrange the list of paths. - Macros - Use the Add, Edit, and Remove buttons to add, edit, or remove a macro identifier. Use the Up and Down buttons to arrange the list of macro identifiers. - Compiler options - Use the Add, Edit, and Remove buttons to add, edit, or remove compiler options. In the Edit Compiler Options dialog, select the tool chain (for example: ARMCC, CW, GCC, GCCE, or MSVC) and enter your custom options. - Linker options - Use the Add, Edit, and Remove buttons to add, edit, or remove linker options. In the Edit Linker Options dialog, select the tool chain (for example: ARMCC, CW, GCC, GCCE, or MSVC) and enter your custom options. - Per-variant include dependencies - Check this option to include dependencies for a specific variant when building a target. For example build a release variant with optimized code, a debug variant with debugging info and a profiling variant with timing hooks. - Disable optimizations in debug builds - Check this option to disable optimizations when building a debug version of your application. Since optimization changes the code created by the compiler, it is best to optimize your code after you have fully tested and debugged it. If a program works in a debug build, but fails in a release build, it is likely that one of the compiler optimizations is exposing a defect in your source code. To isolate the problem, you should disable selected optimizations for each source code file, until you locate the file and the optimization that is causing the problem.
Linker	Linker definition file - Select a linker definition file or click Browse... to locate a definition file. - Export unfrozen - Check this option to tell the build process that exports are not yet frozen. - Don't export library - Check this option to not export a copy of the library. - No strict .def file - Check this option to specify no strict linker definition file. - Compress target executable - Check this option to compress the target executable. - Link as internal name - Specify an internal name. - Win32 base address - Specify the Win32 base address.
Kernel	ASSP ABI - Check this option to build the ASSP application binary interface. - ASSP exports - Check this option to enable ASSP exports.

Name	Function
+ + Runtime	+ + This group allows you to define various runtime options. + Capabilities - Click the Choose... button to select Capabilities. A capability is an access token that corresponds to permission to access sensitive system resources. Platform security permits access to sensitive APIs according to capabilities. Capabilities are used to specify what functionality an application is trusted to use; they are allocated to the application at build time and are policed at run time. Once the capabilities are assigned to the application, they cannot be changed. Thus an application has a set of unalterable capabilities that describe what access the application has to the APIs. + There are three suggested ways to establish which capabilities an application requires. + + The first method is initially to allocate capabilities based on the general operations that the application performs. For example, an instant messaging application would probably require NetworkServices to access the Internet and ReadUserData to read the user’s contacts. + The second method is to use the Symbian Developer Library, which lists the capabilities required by each API. Note that some APIs may be marked as “Dependent”, meaning that the need for the capability depends on the parameters being passed. For example, accessing a file in an application’s private data area requires no capabilities, but accessing a file in \sys\bin requires the AllFiles capability. + The third method is to run the application in the emulator, analyzing the debug file (in the system temporary directory) for capability violations. The output will state the API that caused the violation and what capability was expected. + + Minimum heap size - Set the heap size that you need. + Maximum heap size - Set the heap size that you need. + Stack size - Set the stack size that you need. + Process priority - Select the process priority from the dropdown list. + Secure ID - Enter the Secure ID. The SID is used to determine which private directory a process can access. It is also used to identify the caller applications. An application's SID is defined within its .mmp file, and is used to uniquely identify the application. SID values are requested from the Symbian Signed Web site (www.symbiansigned.com). The Software Installer (SWI) is responsible for ensuring that SIDs are locally unique, i.e., that no two applications have the same SID value on a particular target device. + Vendor ID - Enter the Vendor ID. This ID uniquely identifies the source of the application. If an application needs a VID, it must be certified. Noncertified applications must use a VID of 0 (KNullUid), which is the value applied by default. + Enable debugging (Symbian OS 9.4+) - Activate to enable on-device debugging for Symbian OS 9.4 and later. When activated, the DEBUGGABLE_UDEBONLY flag is added to the project .MMP file. + Paging Mode (Symbian OS 9.3+) - specify the paging mode to: not specified, paged, or unpaged.
+ + Compiler Settings	+ + User includes - Use the Add, Edit, and Remove buttons to add, edit, or remove the paths to the user header files used to compile source files. Use the Up and Down buttons to arrange the list of paths. + System includes - Use the Add, Edit, and Remove buttons to add, edit, or remove the paths to the system header files used to compile source files. Use the Up and Down buttons to arrange the list of paths. + Macros - Use the Add, Edit, and Remove buttons to add, edit, or remove a macro identifier. Use the Up and Down buttons to arrange the list of macro identifiers. + Compiler options - Use the Add, Edit, and Remove buttons to add, edit, or remove compiler options. In the Edit Compiler Options dialog, select the tool chain (for example: ARMCC, CW, GCC, GCCE, or MSVC) and enter your custom options. + Linker options - Use the Add, Edit, and Remove buttons to add, edit, or remove linker options. In the Edit Linker Options dialog, select the tool chain (for example: ARMCC, CW, GCC, GCCE, or MSVC) and enter your custom options. + Per-variant include dependencies - Check this option to include dependencies for a specific variant when building a target. For example build a release variant with optimized code, a debug variant with debugging info and a profiling variant with timing hooks. + Disable optimizations in debug builds - Check this option to disable optimizations when building a debug version of your application. Since optimization changes the code created by the compiler, it is best to optimize your code after you have fully tested and debugged it. If a program works in a debug build, but fails in a release build, it is likely that one of the compiler optimizations is exposing a defect in your source code. To isolate the problem, you should disable selected optimizations for each source code file, until you locate the file and the optimization that is causing the problem.
Linker	Linker definition file - Select a linker definition file or click Browse... to locate a definition file. + Export unfrozen - Check this option to tell the build process that exports are not yet frozen. + Don't export library - Check this option to not export a copy of the library. + No strict .def file - Check this option to specify no strict linker definition file. + Compress target executable - Check this option to compress the target executable. + Link as internal name - Specify an internal name. + Win32 base address - Specify the Win32 base address.
Kernel	ASSP ABI - Check this option to build the ASSP application binary interface. + ASSP exports - Check this option to enable ASSP exports.

Name	Function
- - Project RSS files	- - Select or browse to the resource file to be included in all builds.
- - RSS file path	- - Enter the path to the resource file.
Target file name	Enter the target file name.
Target file path	Select the target file path, such as the executable directory or /resource directory on the target device.
UID 2	Enter the unique identifier. UID2 may need to be a specific value for some kinds of DLLs, especially those used by plug-in frameworks.
UID 3	Enter the unique identifier. In the current implementation of platform security, UID3 is used as the Secure ID if SECUREID is not specified in the .mmp file. If it is specified, UID3 will be used to identify the application as its original purpose. - However, the SID is used to determine which private directory a process can access as well as to identify the caller applications, whereas the UID is used to uniquely identify an application. It is theoretically possible that these two identifiers could have different values, but to avoid confusion Symbian recommends that a SECUREID not be specified in the application's MMP file; UID3 should always be specified instead.
Generate header file	Check this option to generate a header file for the resource files.

Name	Function
+ + Project RSS files	+ + Select or browse to the resource file to be included in all builds.
+ + RSS file path	+ + Enter the path to the resource file.
Target file name	Enter the target file name.
Target file path	Select the target file path, such as the executable directory or /resource directory on the target device.
UID 2	Enter the unique identifier. UID2 may need to be a specific value for some kinds of DLLs, especially those used by plug-in frameworks.
UID 3	Enter the unique identifier. In the current implementation of platform security, UID3 is used as the Secure ID if SECUREID is not specified in the .mmp file. If it is specified, UID3 will be used to identify the application as its original purpose. + However, the SID is used to determine which private directory a process can access as well as to identify the caller applications, whereas the UID is used to uniquely identify an application. It is theoretically possible that these two identifiers could have different values, but to avoid confusion Symbian recommends that a SECUREID not be specified in the application's MMP file; UID3 should always be specified instead.
Generate header file	Check this option to generate a header file for the resource files.

Name	Function
- - Source Folder -	- - Specifies the source folder where the header and source files are - to be created. -
- - Namespace -	- - Select the checkbox to specify whether you want to add the new - class under a namespace or not. If yes, click Browse to select an existing - namespace or type a new namespace. -
- - Class Name -	- - Specifies the name of new C++ class. -
- - Base Classes -	- - Lists all the base types from which the new C++ class is derived. -
- - Method Stubs -	- - Specifies whether to generate stubs for constructor and destructors - of the class. -
- - Use Default -	- - Specifies whether the class declaration and definition are added to - default header and source files or not. -
- - Header -	- - Specifies the header file which contains the class declaration. -
- - Source -	- - Specifies the source file which contains the class definition. -
Use Default	Disable to select different Header and Source files to use as the template for the new class.

Name	Function
+ + Source Folder +	+ + Specifies the source folder where the header and source files are + to be created. +
+ + Namespace +	+ + Select the checkbox to specify whether you want to add the new + class under a namespace or not. If yes, click Browse to select an existing + namespace or type a new namespace. +
+ + Class Name +	+ + Specifies the name of new C++ class. +
+ + Base Classes +	+ + Lists all the base types from which the new C++ class is derived. +
+ + Method Stubs +	+ + Specifies whether to generate stubs for constructor and destructors + of the class. +
+ + Use Default +	+ + Specifies whether the class declaration and definition are added to + default header and source files or not. +
+ + Header +	+ + Specifies the header file which contains the class declaration. +
+ + Source +	+ + Specifies the source file which contains the class definition. +
Use Default	Disable to select different Header and Source files to use as the template for the new class.

Item	Explanation
Macro File	Enter the macro file path and name into the text box or click Browse to locate a macro file.
Use preprocessor symbols from mmp MACRO statements for parsers	Your code will be parsed by the CDT indexer. Enable this option to use MMP macros during parsing.
Show paths and symbols page...	Click to open the Paths and Symbols page under Carbide Build Configuration.

Item	Explanation
PKG File	Choose a PKG file relative to the project's file system or click Browse to locate a PKG file that will be used to create the SIS file. The default option is “none”, which indicates to not build a PKG file.
Signed SIS File Name	Final output signed file name. Default is PKG filename with ‘sisx’ extension.
Certificate	Enter or browse to certificate. - NOTE On Symbian OS 9.x builds, if the key/cert pair are not defined, makekeys will be called and temporary ones will be generated for you to "self-sign" the application. Self-signed applications should be in the - 0xE0000000-0xEFFFFFFF range.
Key	Enter or browse to key. -

Option	Explanation
Panes	Specifies how the memory space is rendered in the pane: - - Address - Binary - Text -
Endian	Choose one of the following: - - Big - Little -
Text	Choose one of the following: - - ISO-8859-1 - US-ASCII - UTF-8 -
Cell size	Specifies the byte size of the memory rendering. The choices include: - - 1 byte - 2 bytes - 4 bytes - 8 bytes -
Radix	Choose one of the following: - - Hex - Decimal Signed - Decimal Unsigned - Octal - Binary -

Item	Explanation
Connetion Name	Enter a name for the connection.
Conection Type	Select the type of connection this setup will use.
Supported Services	Shows a list of services supported by the connection type chosen.

Item	Explanation
Serial Port	A dropdown list of serial ports with known identifiers for selecting the communication port used by the PC to communicate with the device. A named COM port (COM4 - BthModem0) indicates an active port. Unnamed port numbers have usually not been opened and assigned by the PC.
Baud Rate	a dropdown list of baud rates common to serial connections.
Device OS	A dropdown list of device OSes that are supported by the remote agent software. Select the OS used by the device before running a check.
Select a service to test	Click to select a listed service for testing.
Test Service Status	Click Test Service Status to query the remote agent software on the device for its version number. It then compares the version number found with the latest version available for Carbide. A progress bar will appear should the Check TRK version operation requires more than a few seconds. - NOTE The PC must have an internet connection to perform a remote agent version check. - Once the comparison is complete the Status text is updated with the result and further instructions as required. - - If a connection fails, the errors normally fall into these two categories: - - connection failure - this usually indicates the chosen COM port is not open. Try selecting a different COM port, specifically one with a name attached to it (COM4 - BthModem0) for the type of connection you are using (USB or Bluetooth). Repeat as necessary until you get a successful response. - TRK not responding - this indicates that the COM port is open but TRK is not responding. First, verify that TRK is up and running on the device. Second, TRK may be listening on a different COM port, so choose another named COM port and try again. - -

Item	Explanation
Send output to the build console	Enable to direct preprocessor output to a console view. -
Send output to the editor	Enable to direct preprocessor output to an editor. -
CPP arguments	Enter the preprocessor arguments used by the preprocessor. -

Option	Description
From file	Type the name of the file to import from, or click the Browse... button to search for a breakpoints file.
Automatically update existing breakpoints	- When selected, any breakpoints that already exist in your workspace will be overwritten by those being imported from the file. - -
Automatically create breakpoint working sets	- When selected, if an imported breakpoint indicates it belongs to a working set that does not exist in your workspace, the working set will be created for you and the breakpoint added to it. - -

Property	Explanation
Type	The type of item, such as Auto Breakpoint.
File	The path to the file that contains the item.
Line number	Line number in file breakpoint applies to.
Enabled	Indicates the current status of the breakpoint. When checkmarked, the breakpoint stops program execution if its condition is met. When unchecked, the breakpoint is ignored during the debug session.
Condition	The conditional expression associated with the item. This conditional expression must evaluate to true in order for the item to perform its specified action.
Ignore count	Displays the number of times that program execution arrived at the breakpoint before the program stopped.

Menu Bar Layout	Do this…
Views	Select View > System
Macintosh (also applies to Linux/Solaris)	Select View > System Views

Getting Started

Getting Started

Modify

Related concepts

Related tasks

Related references

Modify

Related concepts

Related tasks

Related references

Projects

Related concepts

Related tasks

Related references

Projects

Related concepts

Related tasks

Related references

ARM Registers

Related concepts

Related tasks

Related references

ARM Registers

Related concepts

Related tasks

Related references

Breakpoints

Table 1 Breakpoint—type and states

Breakpoints

Table 1 Breakpoint—type and states

Build System Overview

Basic Build Commands

Command Line Arguments

Other references

Build System Overview

Basic Build Commands

Command Line Arguments

Other references

Common Debugging Actions

Data Viewer Plug-ins

Data Viewer Plug-ins

FPU Registers

Related concepts

Related tasks

Related references

FPU Registers

Related concepts

Related tasks

Related references

General Registers

Related concepts

Related tasks

Related references

General Registers

Related concepts

Related tasks

Related references

Host-specific Registers

Related concepts

Related tasks

Related references

Host-specific Registers

Related concepts

Related tasks

Related references

Carbide Macros

Tasks

Carbide Macros

Tasks

About Symbolics Files

About Symbolics Files

Symbols, .pkg

Symbols, .pkg

Project Templates

Table 1. Available project templates

Related tasks

Project Templates

Table 1. Available project templates

Related tasks

Setting a Thread-specific Conditional Breakpoint