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

Doc: use \uicontrol command instead of \gui macro

Browse Source 
Change-Id: Idc898b6ac70b6d3186d353086b5f3e45830d1f83
Reviewed-by: Topi Reiniö <topi.reinio@digia.com>
This commit is contained in:
Leena Miettinen
2014-12-11 15:43:19 +01:00
committed by Leena Miettinen
parent c9696aa6f4
commit e1fbeedcd4
97 changed files with 1955 additions and 1876 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/src/overview/creator-advanced.qdoc
View File

@@ -86,7 +86,7 @@
\li \l{Showing Task List Files in Issues Pane}
You can load report files created by code scanning and analysis
tools to the \gui Issues output pane. You can navigate to the
tools to the \uicontrol Issues output pane. You can navigate to the
corresponding source code by clicking the error message.
\endlist

38
doc/src/overview/creator-configuring.qdoc
View File

@@ -60,20 +60,20 @@
automatically become available in \QC. If they do not, you must add the kits
yourself to tell \QC where everything is.
To add kits, select \gui Tools > \gui Options > \gui {Build & Run} >
\gui Kits > \gui Add.
To add kits, select \uicontrol Tools > \uicontrol Options > \uicontrol {Build & Run} >
\uicontrol Kits > \uicontrol Add.
For more information, see \l{Adding Kits}.
Each kit consists of a set of values that define one environment, such as a
device, compiler, and Qt version. If you know you have installed a Qt
version, but it is not listed in \gui Tools > \gui Options >
\gui {Build & Run} > \gui {Qt Versions}, you must add it.
version, but it is not listed in \uicontrol Tools > \uicontrol Options >
\uicontrol {Build & Run} > \uicontrol {Qt Versions}, you must add it.
For more information, see \l{Adding Qt Versions}.
Also check that your compiler is listed in \gui Tools > \gui Options >
\gui {Build & Run} > \gui {Compilers}.
Also check that your compiler is listed in \uicontrol Tools > \uicontrol Options >
\uicontrol {Build & Run} > \uicontrol {Compilers}.
For more information, see \l{Adding Compilers}.
@@ -83,7 +83,8 @@
over a WLAN. You must also configure a connection between \QC and the
development PC and specify the device in a kit.
To add devices, select \gui Tools > \gui Options > \gui Devices > \gui Add.
To add devices, select \uicontrol Tools > \uicontrol Options >
\uicontrol Devices > \uicontrol Add.
For more information, see \l{Connecting Mobile Devices}.
@@ -92,7 +93,7 @@
You can use \QC with your favorite keyboard shortcuts.
To view and edit all keyboard shortcuts defined in \QC, select
\gui Tools > \gui Options > \gui Environment > \gui Keyboard.
\uicontrol Tools > \uicontrol Options > \uicontrol Environment > \uicontrol Keyboard.
For more information, see \l{Keyboard Shortcuts}.
@@ -101,8 +102,9 @@
Themes enable you to customize the appearance of the \QC UI: widgets,
colors, and icons.
To switch from the default theme to a dark theme, select \gui Tools >
\gui Options > \gui Environment, and then select \gui Dark in the \gui Theme
To switch from the default theme to a dark theme, select \uicontrol Tools >
\uicontrol Options > \uicontrol Environment, and then select \uicontrol Dark
in the \uicontrol Theme
field.
You can use the \QC text and code editors with your favorite color scheme
@@ -112,8 +114,8 @@
The color schemes apply to highlighting C++ files, QML files, and generic
files.
To change the color scheme, select \gui Tools > \gui Options >
\gui {Text Editor} > \gui {Fonts & Color}.
To change the color scheme, select \uicontrol Tools > \uicontrol Options >
\uicontrol {Text Editor} > \uicontrol {Fonts & Color}.
For more information, see \l{Defining Color Schemes}.
@@ -122,8 +124,8 @@
\l{http://kate-editor.org/2005/03/24/writing-a-syntax-highlighting-file/}
{Kate Editor}. You can download highlight definition files for use with \QC.
To download and use highlight definition files, select \gui Tools >
\gui Options > \gui {Text Editor} > \gui {Generic Highlighter}.
To download and use highlight definition files, select \uicontrol Tools >
\uicontrol Options > \uicontrol {Text Editor} > \uicontrol {Generic Highlighter}.
For more information, see \l{Generic Highlighting}.
@@ -134,8 +136,8 @@
the statement currently under your cursor. You can add, modify,
and remove snippets in the snippet editor.
To open the snippet editor, select \gui Tools > \gui Options >
\gui {Text Editor} > \gui Snippets.
To open the snippet editor, select \uicontrol Tools > \uicontrol Options >
\uicontrol {Text Editor} > \uicontrol Snippets.
For more information, see \l{Editing Code Snippets}.
@@ -146,7 +148,7 @@
\QC. Once it is set up correctly on the development PC, it should just work.
However, some configuration options are available and you can set them in
\gui Tools > \gui Options > \gui{Version Control} > \gui Common.
\uicontrol Tools > \uicontrol Options > \uicontrol{Version Control} > \uicontrol Common.
For more information about the supported functions, see
\l{Using Version Control Systems}.
@@ -164,6 +166,6 @@
manually disable a plugin, it stays disabled even when you upgrade to a
new \QC version, and you must manually enable it to be able to use it.
To enable and disable plugins, select \gui Help > \gui {About Plugins}.
To enable and disable plugins, select \uicontrol Help > \uicontrol {About Plugins}.
*/

2
doc/src/overview/creator-deployment-overview.qdoc
View File

@@ -30,7 +30,7 @@
\title Deploying to Mobile Devices
Deploy configurations in the \gui Project mode \gui {Run Settings} handle
Deploy configurations in the \uicontrol Project mode \uicontrol {Run Settings} handle
the packaging of the application as an executable and copying it to a
location you want to run the executable at. The files can be copied to a
location in the file system of the development PC or a mobile device.

2
doc/src/overview/creator-glossary.qdoc
View File

@@ -84,7 +84,7 @@
cross-platform development easier. Each kit consists of a set
of values that define one environment, such as a device,
tool chain, Qt version, and debugger command to use. Configure kits at
\gui {Tools > Options > Build & Run > Kits}.
\uicontrol {Tools > Options > Build & Run > Kits}.
\row
\li Mode

2
doc/src/overview/creator-help-overview.qdoc
View File

@@ -38,7 +38,7 @@
\QC comes fully integrated with Qt documentation and examples using
the Qt Help plugin. You can add external documentation to the
\gui Help mode and filter the documents displayed to find relevant
\uicontrol Help mode and filter the documents displayed to find relevant
information faster. In addition, you can add bookmarks to help
pages.

4
doc/src/overview/creator-issues.qdoc
View File

@@ -104,7 +104,7 @@
\li Creating new CMake projects with \QC is not supported.
\li If error messages displayed in the \gui {Compile Output} pane contain
\li If error messages displayed in the \uicontrol {Compile Output} pane contain
paths where slashes are missing (for example, C:QtSDK),
check your PATH variable. For more information, see
\l{Troubleshooting MinGW Compilation Errors}.
@@ -117,7 +117,7 @@
\li When debugging executables created by the GNU Compiler version 4.5.0
(all platforms), some data types will not be displayed in the
\gui{Locals and Expressions} view due to missing debug information.
\uicontrol{Locals and Expressions} view due to missing debug information.
\li GDB on Windows may not work if the 'Embassy \reg Security Center'
software by 'Wave \reg Systems' is installed and active (causing

2
doc/src/overview/creator-overview.qdoc
View File

@@ -96,7 +96,7 @@
\QC is integrated to several external native debuggers: GNU
Symbolic Debugger (GDB), Microsoft Console Debugger (CDB), and
internal JavaScript debugger. In the \gui Debug mode, you
internal JavaScript debugger. In the \uicontrol Debug mode, you
can inspect the state of your application while debugging.
The memory and CPU power available on devices are limited and