--- a/core/com.nokia.carbide.cpp.doc.user/html/bugs_fixed.htm Tue Aug 11 13:27:04 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/bugs_fixed.htm Tue Aug 11 14:22:33 2009 -0500
@@ -15,17 +15,22 @@
<body bgcolor="#ffffff">
<h2>Carbide.c++ bugs fixed </h2>
<p>This is a comprehensive list of bugs fixed by release: </p>
-<ul><li><a href="#bugs210">Bugs Fixed in 2.1.0</a></li>
- <li><a href="#bugs204">2.0.4</a>, <a href="#bugs203">2.0.3</a>, <a href="#bugs202"> 2.0.2</a>, <a href="#bugs200">2.0.0</a></li>
+<ul>
+ <li>Bugs Fixed in <a href="#bugs220">2.2.0</a></li>
+ <li><a href="#bugs210">2.1.0</a>, <a href="#bugs204">2.0.4</a>, <a href="#bugs203">2.0.3</a>, <a href="#bugs202"> 2.0.2</a>, <a href="#bugs200">2.0.0</a></li>
<li><a href="#bugs131">1.3.1</a>, <a href="#bugs130">1.3.0</a> , <a href="#bugs122">1.2.2</a>, <a href="#bugs121">1.2.1</a></li>
</ul>
+<h3><a name="bugs220" id="bugs6"></a>Bugs Fixed in v2.2.0</h3>
+<ul>
+ <li><a href="https://xdabug001.ext.nokia.com/bugzilla/show_bug.cgi?id=5391">5391</a> - C++ source hover background color is now customizable. See Window > Preferences > C/C++ > Editor.</li>
+ <li><a href="https://xdabug001.ext.nokia.com/bugzilla/show_bug.cgi?id=9141">9141</a> - Fixed an issue when setting a breakpoint would force a refresh of the Executables view.</li>
+</ul>
<h3><a name="bugs210" id="bugs4"></a>Bugs Fixed in v2.1.0</h3>
<ul>
<li><a href="https://xdabug001.ext.nokia.com/bugzilla/show_bug.cgi?id=9164">9164</a> - Added some diagnostic instrumentation to the Eclipse platform and Carbide to aid users in reporting resource and workspace refreshing issues. </li>
<li><a href="https://xdabug001.ext.nokia.com/bugzilla/show_bug.cgi?id=9310">9310</a> - Can now properly save SBSv2 tools or gcc configurations in the Platform Filtering Preferences panel and added default Apply/Restore controls.</li>
<li><a href="https://xdabug001.ext.nokia.com/bugzilla/show_bug.cgi?id=7351">7351</a> - Fixed an issue where cancelling "Build all configurations" should work and be much faster. </li>
-</ul>
-<ul><li><a href="https://xdabug001.ext.nokia.com/bugzilla/show_bug.cgi?id=8500">8500</a> - Fixed an issue that when importing symbols where certain symbols contained erroneous address data. </li>
+ <li><a href="https://xdabug001.ext.nokia.com/bugzilla/show_bug.cgi?id=8500">8500</a> - Fixed an issue that when importing symbols where certain symbols contained erroneous address data. </li>
<li><a href="https://xdabug001.ext.nokia.com/bugzilla/show_bug.cgi?id=8816">8816</a> - Bash errors should now appear in the Problems view. </li>
<li><a href="https://xdabug001.ext.nokia.com/bugzilla/show_bug.cgi?id=8901">8901</a> - Fixed an issue in the error parser that prevented building Phone Debug builds due to Assembler warnings. </li>
<li><a href="https://xdabug001.ext.nokia.com/bugzilla/show_bug.cgi?id=8914">8914</a> - Corrected an issue with scanning SDKs that cause the scan to repeat endlessly. </li>
--- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/toggling_breakpoints.htm Tue Aug 11 13:27:04 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/toggling_breakpoints.htm Tue Aug 11 14:22:33 2009 -0500
@@ -1,38 +1,38 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Enabling, Disabling and Removing Breakpoints</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2> Enabling, Disabling and Removing Breakpoints </h2>
-<p>Use the <b>Toggle Breakpoint</b> command (<span class="code">Ctrl+Shift+B</span>) to set a regular breakpoint in an <a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_editor_view.htm">Editor</a> or <a href="../../reference/view_disassembly.htm">Disassembly</a> view. Only a single breakpoint can exist on a source code line. A regular breakpoint suspends program execution when it is hit, or executed, during a debug session. The debugger executes the line of source code that contains the regular breakpoint, then opens the <a href="../../reference/perspective_debug.htm">Debug</a> perspective to allow examination and modification.</p>
-<p>If a regular breakpoint already exists on the selected line, as indicated by the enabled breakpoint badge (<img src="../../tasks/breakpoints/images/breakpoints_enabled_icon.png" width="9" height="10" align="baseline">) in the marker bar, use <b>Toggle Breakpoint</b> to remove the breakpoint.</p>
-<h4>Enabling and Disabling breakpoints</h4>
-<p>Once a source line is selected in an editor or Disassembly view, the methods of toggling breakpoints to be enabled of disabled include: </p>
-<ul>
- <li>Choose the <b>Run > Toggle Breakpoint</b> menu option</li>
- <li>Right-click and choose <b>Toggle Breakpoint</b> from the context menu</li>
- <li>Press <span class="code">Ctrl+Shift+B</span> </li>
- <li>Double-click in the marker bar to enable or disable a breakpoint on that source line </li>
-</ul>
-<h4>Removing breakpoints</h4>
-<p>In the <a href="../../reference/view_breakpoints.htm">Breakpoints</a> view, locate the source code line to modify and: </p>
-<ul>
- <li>Right-click the breakpoint and choose <b>Remove</b> from the context menu to remove the breakpoint </li>
-</ul>
-<p class="note"><strong>NOTE</strong> Once a breakpoint is removed from the Breakpoints view it cannot be recovered using the Breakpoints view, it must be set in an editor or disassembly view. </p>
-<p>Breakpoints must first be loaded and resolved before they can be hit during a debug session. See <a href="resolving_breakpoints.htm">Resolving Breakpoint States</a> for more information on the various states a breakpoint can exhibit. </p>
-<p>See <a href="exporting_breakpoints.htm">Saving and importing breakpoints</a> for information on storing breakpoint data sets for sharing or re-use. </p>
-<p class="note"><strong>TIP</strong> If you find that a breakpoint is not being hit during a debug session, verify that the EXE or DLL is listed in the <a href="../../reference/view_executables.htm">Executables</a> view. </p>
-<p class="note"><strong>TIP</strong> If debugging a server launched by a client, you must attach to the server process using the <a href="../../reference/view_symbian_kernel.htm">Symbian OS Data</a> view in order to hit the breakpoints in the server. Alternately, you can launch the server and client as two independent EXEs using the same COM port and debug them that way.</p>
-<h4>Other references</h4>
-<ul>
- <li><a href="breakpoints.htm">Breakpoints overview </a></li>
-</ul>
-<div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Enabling, Disabling and Removing Breakpoints</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2> Enabling, Disabling and Removing Breakpoints </h2>
+<p>Use the <b>Toggle Breakpoint</b> command (<span class="code">Ctrl+Shift+B</span>) to set a regular breakpoint in an <a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_editor_view.htm">Editor</a> or <a href="../../reference/view_disassembly.htm">Disassembly</a> view. Only a single breakpoint can exist on a source code line. A regular breakpoint suspends program execution when it is hit, or executed, during a debug session. The debugger executes the line of source code that contains the regular breakpoint, then opens the <a href="../../reference/perspective_debug.htm">Debug</a> perspective to allow examination and modification.</p>
+<p>If a regular breakpoint already exists on the selected line, as indicated by the enabled breakpoint badge (<img src="../../tasks/breakpoints/images/breakpoints_enabled_icon.png" width="9" height="10" align="baseline">) in the marker bar, use <b>Toggle Breakpoint</b> to remove the breakpoint.</p>
+<h4>Enabling and Disabling breakpoints</h4>
+<p>Once a source line is selected in an editor or Disassembly view, the methods of toggling breakpoints to be enabled of disabled include: </p>
+<ul>
+ <li>Choose the <b>Run > Toggle Breakpoint</b> menu option</li>
+ <li>Right-click and choose <b>Toggle Breakpoint</b> from the context menu</li>
+ <li>Press <span class="code">Ctrl+Shift+B</span> </li>
+ <li>Double-click in the marker bar to enable or disable a breakpoint on that source line </li>
+</ul>
+<h4>Removing breakpoints</h4>
+<p>In the <a href="../../reference/view_breakpoints.htm">Breakpoints</a> view, locate the source code line to modify and: </p>
+<ul>
+ <li>Right-click the breakpoint and choose <b>Remove</b> from the context menu to remove the breakpoint </li>
+</ul>
+<p class="note"><strong>NOTE</strong> Once a breakpoint is removed from the Breakpoints view it cannot be recovered using the Breakpoints view, it must be set in an editor or disassembly view. </p>
+<p>Breakpoints must first be loaded and resolved before they can be hit during a debug session. See <a href="resolving_breakpoints.htm">Resolving Breakpoint States</a> for more information on the various states a breakpoint can exhibit. </p>
+<p>See <a href="exporting_breakpoints.htm">Saving and importing breakpoints</a> for information on storing breakpoint data sets for sharing or re-use. </p>
+<p class="note"><strong>TIP</strong> If you find that a breakpoint is not being hit during a debug session, verify that the EXE or DLL is listed in the <a href="../../reference/view_executables.htm">Executables</a> view. </p>
+<p class="note"><strong>TIP</strong> If debugging a server launched by a client, you must attach to the server process using the <a href="../../reference/view_symbian_kernel.htm">Symbian OS Data</a> view in order to hit the breakpoints in the server. Alternately, you can launch the server and client as two independent EXEs using the same COM port and debug them that way.</p>
+<h4>Other references</h4>
+<ul>
+ <li><a href="breakpoints.htm">Breakpoints overview </a></li>
+</ul>
+<div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+</body>
+</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/release_notes.htm Tue Aug 11 13:27:04 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/release_notes.htm Tue Aug 11 14:22:33 2009 -0500
@@ -42,7 +42,7 @@
</ul>
<ul>
<li><b>CDT 6.0 </b>— The final version of CDT included as part of the Galileo release. See the <a href="http://wiki.eclipse.org/CDT/User/NewIn60">CDT 6.0 News and Noteworthy</a> page for more information.</li>
- <li><b>Java 6.0 </b>— Due to the above changes Carbide has also updated to use the Java 6.0 VM. See <a href="http://java.sun.com/javase/6/webnotes/features.html">Java SE 6 Release Notes</a> page for more information.</li>
+ <li><b>Java 6.0 </b>— Due to the above changes Carbide has also updated to use the Java Runtime Environment (JRE) 6.0. See <a href="http://java.sun.com/javase/6/webnotes/features.html">Java SE 6 Release Notes</a> page for more information.</li>
</ul>
<h4>2.1.0</h4>
<ul>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/AddinganSDK.html Tue Aug 11 13:27:04 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/AddinganSDK.html Tue Aug 11 14:22:33 2009 -0500
@@ -9,7 +9,7 @@
<p>
The Symbian OS plug-ins can usually detect when a SDK has been installed,
- as described in <a href="../concepts/SDKSupport.html">SDK Support</a>.</p>
+ as described in <a href="WorkingwithSDKs.html">SDK Support</a>.</p>
<p>
To do this:
</p>
Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/watchpoints/images/icon_watchpoint_write_resolved.png has changed