forked from qt-creator/qt-creator
Doc: Document toggling visibility of menu items
Debug, Analyze, and Build menu items are invisible by default. Visibility can be toggled from Options. Task-number: QDS-6372 Change-Id: I5134868e8cd08c229b6c3a8ff3c53a1cc67949ab Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
This commit is contained in:
@@ -49,6 +49,13 @@
|
|||||||
For more information about all the options you have, see
|
For more information about all the options you have, see
|
||||||
\l{Debugging Qt Quick Projects}.
|
\l{Debugging Qt Quick Projects}.
|
||||||
|
|
||||||
|
\if defined(qtdesignstudio)
|
||||||
|
\note In this section, you are using advanced menu items. These are not
|
||||||
|
visible by default. To toggle the visibility of advanced menu items, see
|
||||||
|
\l{Customizing the Menu}.
|
||||||
|
|
||||||
|
\endif
|
||||||
|
|
||||||
The Same Game demo shows how to write a game in QML, using JavaScript for
|
The Same Game demo shows how to write a game in QML, using JavaScript for
|
||||||
all the game logic. Open the demo project in \QC to debug it:
|
all the game logic. Open the demo project in \QC to debug it:
|
||||||
|
|
||||||
|
@@ -48,6 +48,12 @@
|
|||||||
For an example of how to debug Qt Quick Projects, see
|
For an example of how to debug Qt Quick Projects, see
|
||||||
\l{Debugging a Qt Quick Example Application}.
|
\l{Debugging a Qt Quick Example Application}.
|
||||||
|
|
||||||
|
\if defined(qtdesignstudio)
|
||||||
|
\note In this section, you are using advanced menu items. These are not
|
||||||
|
visible by default. To toggle the visibility of advanced menu items, see
|
||||||
|
\l{Customizing the Menu}.
|
||||||
|
\endif
|
||||||
|
|
||||||
\section1 Setting Up QML Debugging
|
\section1 Setting Up QML Debugging
|
||||||
|
|
||||||
\if defined(qtcreator)
|
\if defined(qtcreator)
|
||||||
|
@@ -80,6 +80,12 @@
|
|||||||
{Chrome Trace Format Viewer}.
|
{Chrome Trace Format Viewer}.
|
||||||
\endif
|
\endif
|
||||||
|
|
||||||
|
\if defined(qtdesignstudio)
|
||||||
|
\note In this section, you are using advanced menu items. These are not
|
||||||
|
visible by default. To toggle the visibility of advanced menu items, see
|
||||||
|
\l{Customizing the Menu}.
|
||||||
|
\endif
|
||||||
|
|
||||||
\section1 Using QML Profiler
|
\section1 Using QML Profiler
|
||||||
|
|
||||||
To monitor the performance of an application in the QML Profiler:
|
To monitor the performance of an application in the QML Profiler:
|
||||||
|
@@ -132,6 +132,27 @@
|
|||||||
\uicontrol Keyboard
|
\uicontrol Keyboard
|
||||||
\endtable
|
\endtable
|
||||||
|
|
||||||
|
\if defined(qtdesignstudio)
|
||||||
|
\section1 Customizing the Menu
|
||||||
|
|
||||||
|
By default, top-level menu items \uicontrol Build, \uicontrol Debug, and
|
||||||
|
\uicontrol Analyze are not visible. These menu items contain options for
|
||||||
|
advanced functionality.
|
||||||
|
|
||||||
|
To toggle the visibility of these menu items:
|
||||||
|
\list 1
|
||||||
|
\li Go to \uicontrol Tools > \uicontrol Options.
|
||||||
|
\li On the \uicontrol Environment tab, select
|
||||||
|
\uicontrol{Qt Design Studio Configuration}.
|
||||||
|
\li Clear the checkbox for the items that you want to be visible.
|
||||||
|
\endlist
|
||||||
|
|
||||||
|
\image studio-menu-item-visibility.png
|
||||||
|
|
||||||
|
You need to restart \QDS to apply changes made to these settings.
|
||||||
|
|
||||||
|
\endif
|
||||||
|
|
||||||
\section1 Switching UI Themes
|
\section1 Switching UI Themes
|
||||||
|
|
||||||
Themes enable you to change the appearance of the UI from dark to light,
|
Themes enable you to change the appearance of the UI from dark to light,
|
||||||
|
BIN
doc/qtdesignstudio/images/studio-menu-item-visibility.png
Normal file
BIN
doc/qtdesignstudio/images/studio-menu-item-visibility.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 14 KiB |
@@ -30,6 +30,10 @@
|
|||||||
|
|
||||||
\title Designer-Developer Workflow
|
\title Designer-Developer Workflow
|
||||||
|
|
||||||
|
\note In this section, you are using advanced menu items. These are not
|
||||||
|
visible by default. To toggle the visibility of advanced menu items, see
|
||||||
|
\l{Customizing the Menu}.
|
||||||
|
|
||||||
\QDS enables designers and developers to work together on common
|
\QDS enables designers and developers to work together on common
|
||||||
projects to develop applications. Designers use the \l{Design Views}{views}
|
projects to develop applications. Designers use the \l{Design Views}{views}
|
||||||
in the \uicontrol Design mode to modify \l{UI Files}{UI files} (\e .ui.qml),
|
in the \uicontrol Design mode to modify \l{UI Files}{UI files} (\e .ui.qml),
|
||||||
|
@@ -30,6 +30,10 @@
|
|||||||
|
|
||||||
\title Exporting Components
|
\title Exporting Components
|
||||||
|
|
||||||
|
\note In this section, you are using advanced menu items. These are not
|
||||||
|
visible by default. To toggle the visibility of advanced menu items, see
|
||||||
|
\l{Customizing the Menu}.
|
||||||
|
|
||||||
\l{glossary-component}{Components} contained in \l{UI Files}
|
\l{glossary-component}{Components} contained in \l{UI Files}
|
||||||
{UI files} (.ui.qml) can be exported to JSON metadata format and PNG assets.
|
{UI files} (.ui.qml) can be exported to JSON metadata format and PNG assets.
|
||||||
|
|
||||||
|
@@ -30,6 +30,10 @@
|
|||||||
|
|
||||||
\title Packaging Applications
|
\title Packaging Applications
|
||||||
|
|
||||||
|
\note In this section, you are using advanced menu items. These are not
|
||||||
|
visible by default. To toggle the visibility of advanced menu items, see
|
||||||
|
\l{Customizing the Menu}.
|
||||||
|
|
||||||
When you are ready to deliver your application to users or upload it to
|
When you are ready to deliver your application to users or upload it to
|
||||||
app stores, you can use \QDS to create suitable packages that contain all
|
app stores, you can use \QDS to create suitable packages that contain all
|
||||||
the necessary files, such as fonts, images, components, and modules.
|
the necessary files, such as fonts, images, components, and modules.
|
||||||
|
Reference in New Issue
Block a user