1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-07-23 00:45:28 +02:00

fixes for user docs

This commit is contained in:
Vivian Kong 2009-07-29 14:31:33 +00:00
parent b86829cf94
commit 32b3cb1228
5 changed files with 20 additions and 20 deletions

View file

@ -38,7 +38,7 @@ may contain other information.
<p align="right"><b>Rename in File</b></p>
</td>
<td>To make rename refactoring work interactively in the editor,
position the cursor on an identifier in the editor and hit Cntl-1
position the cursor on an identifier in the editor and hit Ctrl-1
(the hotfix key). Choose "Rename in file."
Changing an identifier simultaneously changes all other references to that identifier.
<p><img src="../images/60/RenameInFile.png" alt="Rename in File">
@ -263,7 +263,7 @@ may contain other information.
</li>
<li>Context menu actions on Working Sets in the Project Explorer for activating and building configurations
<p><img src="../images/60/New_cdtwsconfig_wsContextMenu.png" alt="Activating and building working set configurations through context menu"/></p>
<p><img src="../images/60/New_cdtwsconfig_wsContextMenu.png" alt="Activating and building working set configurations through context menu"></p>
</li>
<li>For more details, see the <a href="http://wiki.eclipse.org/CDT/designs/workingSets">working sets
@ -306,8 +306,7 @@ may contain other information.
<li>RSE EFS projects and EFS resources are supported.</li>
<li>Improved performance.</li>
</ul>
<p><img src="../images/60/EPM-multi.png" alt="More accurate algorithm for associating errors/warnings from build output with files in the
workspace">
<p><img src="../images/60/EPM-multi.png" alt="More accurate algorithm for associating errors/warnings from build output with files in the workspace">
<p>In the <b>Problems View</b>, external file locations (outside of the workspace) have been moved to the Location
column and associated with "Open External Location" menu.
<p><img src="../images/60/PV-extloc.png" alt="Open External Location from context menu in Problems View">
@ -387,6 +386,7 @@ may contain other information.
</td>
</tr>
-->
</tbody>
</table>
<p><a href="#top">Back to Top</a> <!-- ******************** CDT 5.0 info ********************** -->
<h1 id="5.0">CDT 5.0 - New and Noteworthy</h1>

View file

@ -42,7 +42,7 @@ function newWin(url) {
<li>In the <b>Location</b> field, specify the path to the existing files for your project.
<li>From the <b>Project types</b> list, expand <b>Makefile Project</b> and select <b>Empty Project.</b>.
<ul>
<li>To have sample source and a makefile created in your existing directory, select <b>Hello World C++ Project</b</li>
<li>To have sample source and a makefile created in your existing directory, select <b>Hello World C++ Project</b></li>
</ul>
<li>Make sure a toolchain is selected.</li>

View file

@ -47,14 +47,14 @@ using namespace std;
int main () {
// Say Hello five times
for (int index = 0; index < 5; ++index)
cout << "HelloWorld!" << endl;
for (int index = 0; index &lt; 5; ++index)
cout &lt;&lt; "HelloWorld!" &lt;&lt; endl;
char input = 'i';
cout << "To exit, press 'm'" << endl;
cout &lt;&lt; "To exit, press 'm'" &lt;&lt; endl;
while(input != 'm') {
cin >> input;
cout << "You just entered " << input
<< " you need to enter m to exit." << endl;
cout &lt;&lt; "You just entered " &lt;&lt; input
&lt;&lt; " you need to enter m to exit." &lt;&lt; endl;
}
exit(0);
}
@ -93,4 +93,4 @@ can build your HelloWorld project, you must create a makefile.</p>
<img src="../images/ng00_04a.gif" ALT="IBM Copyright Statement" >
</body>
</html>
</html>

View file

@ -13,9 +13,9 @@
<h1>Run and Debug</h1>
<p>Types of Launch configurations supported by CDT</p>
<img src="../images/trans.gif" border="0" width="25" height="1" alt="">C/C++ Local Application - run application on local host<br/>
<img src="../images/trans.gif" border="0" width="25" height="1" alt="">C/C++ Attach to Local Application - attach to already running application on the local host<br/>
<img src="../images/trans.gif" border="0" width="25" height="1" alt="">C/C++ Postmortem debugger - run debugger on "core" file<br/>
<img src="../images/trans.gif" border="0" width="25" height="1" alt="">C/C++ Local Application - run application on local host<br>
<img src="../images/trans.gif" border="0" width="25" height="1" alt="">C/C++ Attach to Local Application - attach to already running application on the local host<br>
<img src="../images/trans.gif" border="0" width="25" height="1" alt="">C/C++ Postmortem debugger - run debugger on "core" file<br>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_u_run_gdb_launch_group.htm">Launch Group</a> - launch multiple applications<br>
<p>Launch Configurations common tabs</p>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_u_run_dbg_main.htm">Main</a><br>
@ -28,4 +28,4 @@
<p><img src="../images/ng00_04a.gif" ALT="IBM Copyright Statement" ></p>
</body>
</html>
</html>

View file

@ -56,14 +56,14 @@ The <i>Common</i> tab lets you select where the configuration is stored, see <a
and <br>
2. It establishes a 'mode' filter for the launch configurations that are
exposed to the user (for selection) in the area below the combobox<br>
<p/>
<p>
For example, when the 'debug' mode is selected, (1) only launch configurations
that support being invoked in 'debug' mode appear. Also, (2) when the launch
group is invoked, that particular child launch configuration will be invoked in
'debug' mode.
</td></tr>
<tr><td><dt>Filter input</dt></td><td>Type in filter input to filter list of configurations by name</td></tr>
<tr><td><dt>Configurations tree</dt></td><td>Lists all available launch configurations for the selected Launch Mode, filtered by <i>Filter input<i>.</td></tr>
<tr><td><dt>Configurations tree</dt></td><td>Lists all available launch configurations for the selected Launch Mode, filtered by <i>Filter input</i>.</td></tr>
<tr><td><dt>Use default mode when launching</dt></td>
<td>
This checkbox acts as a sort of override to whatever mode is set in the Launch Mode
@ -77,7 +77,7 @@ the "Use default..." checkbox, you're saying: "launch this particular child
configuration in the mode that the parent (launch group) is launched with." If
you do not have that checkbox checked, then the child configurations will be
invoked in whatever mode each individual child is configured with.
<p/>
<p>
Note that "Use default..." control can allow you to create a launch group
that will not be successful. For example when one or more launch configurations
selected cannot be launched in the mode dictated by launch group mode.
@ -93,7 +93,7 @@ There are several actions available that control what should be done after each
</dl>
<p/>
<p>
@ -113,4 +113,4 @@ There are several actions available that control what should be done after each
</body>
</html>
</html>