feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

Doc: Reformatting

Browse Source 
No text change

Change-Id: I13d959e9c9204628775abbcb53a1b824d1b62578
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@theqtcompany.com>
This commit is contained in:
Tobias Hunger
2015-06-18 10:35:41 +02:00
parent 113d253f13
commit 1414c3ed2f
2 changed files with 43 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
doc/src/analyze/creator-clang-static-analyzer.qdoc
View File

@@ -70,4 +70,3 @@
\inlineimage qtcreator-analyze-start-button.png \inlineimage qtcreator-analyze-start-button.png
(\uicontrol Start) button. (\uicontrol Start) button.
*/ */

84
doc/src/howto/creator-cli.qdoc
View File

@@ -30,8 +30,8 @@
\title Using Command Line Options \title Using Command Line Options
You can start \QC and specify some options from the command line. You can start \QC and specify some options from the command line. For
For example, you can open a file to any line. example, you can open a file to any line.
To specify command line options, enter the following command in the \QC To specify command line options, enter the following command in the \QC
installation or build directory: installation or build directory:
@@ -62,9 +62,10 @@
\endlist \endlist
To open a project that is located in a particular folder, you can pass on the folder To open a project that is located in a particular folder, you can pass on
name as a command line argument. \QC looks for a session that matches the folder name and the folder name as a command line argument. \QC looks for a session that
loads it. Or it looks for a project file in the folder and opens it. For example: matches the folder name and loads it. Or it looks for a project file in the
folder and opens it. For example:
\c {qtcreator .} \c {qtcreator .}
@@ -153,8 +154,9 @@
stylesheets. stylesheets.
\row \row
\li -debug <pid> \li -debug <pid>
\li Debugger plugin: attach to the process with the given process ID. \li Debugger plugin: attach to the process with the given process
ID.
\row \row
\li -debug <executable>[,kit=<kit>] \li -debug <executable>[,kit=<kit>]
@@ -164,53 +166,53 @@
and sysroots. and sysroots.
\row \row
\li -debug [executable,]core=<corefile>[,kit=<kit>] \li -debug [executable,]core=<corefile>[,kit=<kit>]
\li Debugger plugin: load the core file named \c{corefile}. \li Debugger plugin: load the core file named \c{corefile}.
The parameter \c{executable} specifies the executable that The parameter \c{executable} specifies the executable that
produced the core file. produced the core file.
If this parameter is omitted, \QC will attempt to reconstruct If this parameter is omitted, \QC will attempt to reconstruct
it from the core file itself. it from the core file itself. This will fail for paths with more
This will fail for paths with more than about 80 characters. than about 80 characters.
In such cases the \c{executable} parameter is mandatory. In such cases the \c{executable} parameter is mandatory.
A \c{kit} can be specified to point to non-default debuggers A \c{kit} can be specified to point to non-default debuggers
and sysroots. and sysroots.
\row \row
\li -debug <executable>,server=<server:port>[,kit=<kit>] \li -debug <executable>,server=<server:port>[,kit=<kit>]
\li Debugger plugin: attach to a debug server running on the port \li Debugger plugin: attach to a debug server running on the port
\c{port} on the server \c{server}. The parameter \c{executable} \c{port} on the server \c{server}. The parameter \c{executable}
specifies a local copy of the executable the remote debug server is specifies a local copy of the executable the remote debug server
manipulating. is manipulating.
A \c{kit} can be specified to point to non-default debuggers A \c{kit} can be specified to point to non-default debuggers and
and sysroots. sysroots.
\row \row
\li -wincrashevent <event-handle:pid> \li -wincrashevent <event-handle:pid>
\li Debugger plugin: Attach to crashed processes by using the specified \li Debugger plugin: Attach to crashed processes by using the
event handle and process ID. specified event handle and process ID.
\row \row
\li -customwizard-verbose \li -customwizard-verbose
\li ProjectExplorer plugin: display additional information when loading \li ProjectExplorer plugin: display additional information when
custom wizards. For more information about custom wizards, see loading custom wizards. For more information about custom
\l{Adding New Custom Wizards} wizards, see \l{Adding New Custom Wizards}
\row \row
\li -lastsession \li -lastsession
\li ProjectExplorer plugin: load the last session when \QC starts. \li ProjectExplorer plugin: load the last session when \QC starts.
Open the projects and files that were open when you last exited \QC. Open the projects and files that were open when you last exited
For more information about managing sessions, see \l{Managing Sessions}. \QC. For more information about managing sessions, see
\l{Managing Sessions}.
\endtable \endtable
\section1 Using Custom Styles \section1 Using Custom Styles
\QC is a \l{QApplication} \QC is a \l{QApplication}{Qt application}, and therefore, it accepts the
{Qt application}, and therefore, it accepts the command line options command line options that all Qt applications accept. For example, you can
that all Qt applications accept. For example, you can use the \c {-style} and use the \c {-style} and \c {-stylesheet} options to apply custom styles and
\c {-stylesheet} options to apply custom styles and \l{Qt Style Sheets}{stylesheets}. The styling is only applied during the
\l{Qt Style Sheets}{stylesheets}. current session.
The styling is only applied during the current session.
Exercise caution when applying styles, as overriding the existing styling Exercise caution when applying styles, as overriding the existing styling
may make some items difficult to see. Also, setting a stylesheet may affect may make some items difficult to see. Also, setting a stylesheet may affect