forked from qt-creator/qt-creator
Doc: Add more content to FAQ
Change-Id: Ia3b475bd02116f0c8d9cc778ab270603b802dab4 Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
This commit is contained in:
@@ -73,6 +73,23 @@
|
||||
them to \QDS as assets. \QDS deploys them to devices when you preview the
|
||||
UI. For more information, see \l{Using Custom Fonts}.
|
||||
|
||||
\section2 Items You Can Export
|
||||
|
||||
You can export the following parts of your design using \QBF:
|
||||
\list
|
||||
\li Images
|
||||
\li Vector images
|
||||
\li Layers
|
||||
\list
|
||||
\li Text layers
|
||||
\li Shape layers
|
||||
\endlist
|
||||
\li Components
|
||||
\li Component instances
|
||||
\li Frames
|
||||
\li Groups
|
||||
\endlist
|
||||
|
||||
\section2 Using Frames
|
||||
|
||||
Frames are exported as components of the \l Rectangle type by default.
|
||||
|
@@ -54,6 +54,22 @@
|
||||
such as \e {.psd} and \e {.psb}. For all other document formats, \QDS
|
||||
displays the following error message: \e {Document is not supported.}
|
||||
|
||||
\section2 Items You Can Export
|
||||
|
||||
You can export the following parts of your design using \QBPS:
|
||||
\list
|
||||
\li Layers
|
||||
\li Text layers
|
||||
\li Groups
|
||||
\li Artboards
|
||||
\endlist
|
||||
|
||||
You cannot export the following parts of your design:
|
||||
\list
|
||||
\li Smart Objects
|
||||
\li Frames
|
||||
\endlist
|
||||
|
||||
\section2 Using Artboards
|
||||
|
||||
The relationships between the groups and layers on an artboard are preserved
|
||||
|
@@ -82,6 +82,25 @@
|
||||
{Sketch Bridge Tutorial Part 2}
|
||||
\endlist
|
||||
|
||||
\section2 Items You Can Export
|
||||
|
||||
You can export the following parts of your design using \QBSK:
|
||||
\list
|
||||
\li Layers
|
||||
\list
|
||||
\li Shape layers
|
||||
\li Vector layers
|
||||
\li Pencil layers
|
||||
\li Slice layers
|
||||
\li Text layers
|
||||
\endlist
|
||||
\li Groups
|
||||
\li Artboards
|
||||
\li Hotspots
|
||||
\li Symbols
|
||||
\li Libraries
|
||||
\endlist
|
||||
|
||||
\section2 Using Artboards
|
||||
|
||||
The relationships between artboards and layers are preserved when you export
|
||||
|
@@ -36,11 +36,22 @@
|
||||
\l{Using the Help Mode}{Help mode}. Many questions are also answered by the
|
||||
\l{Examples and Tutorials}{examples and video tutorials}.
|
||||
|
||||
\section1 \QB
|
||||
\section2 How does \QBPS differ from \QBSK?
|
||||
\list
|
||||
\li \l {FAQ - \QB}{\QB}
|
||||
\li \l {FAQ - Assets}{Assets}
|
||||
\li \l {FAQ - Components}{Components}
|
||||
\li \l {FAQ - Views}{Views}
|
||||
\li \l {FAQ - Integration Between \QDS and \QC}{Integration Between \QDS and \QC}
|
||||
\li \l {FAQ - Performance}{Performance}
|
||||
\li \l {FAQ - Data Simulation}{Data Simulation}
|
||||
\endlist
|
||||
|
||||
Visually, \QBPS and \QBSK, and \QBF are identical. The biggest difference
|
||||
between \QBPS and \QBSK is that \QBSK can export .svg (vector), .png and
|
||||
\section1 FAQ - \QB
|
||||
|
||||
\section2 How does \QBPS differ from \QBSK and \QBF?
|
||||
|
||||
\QBPS, \QBSK, and \QBF are functionally similar. The biggest difference
|
||||
between the tools is that \QBSK and \QBF can export .svg (vector), .png, and
|
||||
.jpeg files, while \QBPS only supports .png and .jpeg. Adobe Illustrator
|
||||
users can port their designs into Photoshop, but they must be rasterized
|
||||
into \e {smart objects}.
|
||||
@@ -48,21 +59,60 @@
|
||||
For more information, see \l {Exporting from Design Tools}.
|
||||
|
||||
\section2 Do I need to copy the .qml files in the resource folder after each design modification?
|
||||
|
||||
No you don't. When you add new or modified .metadata files to your project
|
||||
from Photoshop, \QBPS, or \QBSK, select the \uicontrol {Merge QML} check
|
||||
box in the \uicontrol {Asset Import} dialog to merge the changes into
|
||||
from Photoshop, \QBPS, \QBSK, or \QBF, select the \uicontrol {Merge QML}
|
||||
check box in the \uicontrol {Asset Import} dialog to merge the changes into
|
||||
existing QML files instead of overwriting them.
|
||||
|
||||
For more information, see \l {Importing 2D Assets}.
|
||||
|
||||
\section1 Using 3D Components
|
||||
\section2 Where can I find log files generated by \QB while exporting metadata?
|
||||
|
||||
On Windows, the logs are stored inside the temp folder in
|
||||
\c {C:\Users\<USERNAME>\AppData\Local\Temp}. The log files are named as
|
||||
\e csxs<versionNumber>-<HostID>.log. Please note that you might have to set
|
||||
the log level to generate logs. Also note the CEP version while setting the
|
||||
log level. The CEP version depends on the Photoshop version you are using.
|
||||
Currently the latest version is version 10.
|
||||
|
||||
\section1 FAQ - Assets
|
||||
|
||||
\section2 Can I import my organization's preferred font in \QDS?
|
||||
|
||||
Yes, you can import your custom fonts, for example, in .ttf or .otf formats.
|
||||
Fonts installed on your system will be available to use in your imported
|
||||
designs. If you need to deploy the device, you will have to import the font
|
||||
into the project.
|
||||
|
||||
For more information, see \l {Using Custom Fonts}.
|
||||
|
||||
\section1 FAQ - Components
|
||||
|
||||
\section2 Can custom components be used?
|
||||
|
||||
Yes, you can create custom components and controls by using wizard templates
|
||||
or move component instances into separate files to turn them into new
|
||||
components that you can create instances of. For more information, see
|
||||
\l {Creating Components}.
|
||||
|
||||
\section2 What are the 3D import formats for \QDS?
|
||||
|
||||
You can import files stored in several widely-used formats, such as .fbx,
|
||||
.obj, .gltf, .glb, .blend, .dae, .uia, and .uip.
|
||||
|
||||
For more information, see \l {Importing 3D Assets}
|
||||
For more information, see \l {Importing 3D Assets}.
|
||||
|
||||
\section2 How to integrate custom C++ components into QDS?
|
||||
|
||||
You must create your own QML module that contains the components and
|
||||
provides additional information about your components. For more information,
|
||||
see \l {Using QML Modules with Plugins}.
|
||||
|
||||
\section1 FAQ - Views
|
||||
|
||||
\section2 What are the keyboard shortcuts for moving around in \uicontrol {3D Editor}?
|
||||
|
||||
\section2 What are the keyboard shortcuts for moving around in \uicontrol {3D Editor?}
|
||||
\list
|
||||
\li To pan: \key Alt + middle mouse button
|
||||
\li To orbit (rotate): \key Alt (or \key Option on \macos) + left mouse button
|
||||
@@ -71,7 +121,8 @@
|
||||
|
||||
For more information, see \l {3D Editor}.
|
||||
|
||||
\section1 Integration Between \QDS and \QC
|
||||
\section1 FAQ - Integration Between \QDS and \QC
|
||||
|
||||
\section2 Is there a way to automatically propagate name changes between \QDS and \QC?
|
||||
|
||||
Unfortunately we do not automate renaming files between tools at the moment.
|
||||
@@ -89,15 +140,22 @@
|
||||
configuration and source files, as instructed in
|
||||
\l {Converting UI Projects to Applications}.
|
||||
|
||||
\section1 Performance
|
||||
\section1 FAQ - Performance
|
||||
|
||||
\section2 Will my application with 3D components run at 60 FPS?
|
||||
|
||||
With the ability to test the full (2D/3D) UI in \QDS on target hardware,
|
||||
you will quickly be able to determine if a 3D object is causing performance
|
||||
issues using the \uicontrol FPS display in \uicontrol Design mode.
|
||||
issues using the \uicontrol FPS field in the \uicontrol Design mode.
|
||||
\uicontrol FPS displays the frames-per-second (FPS) refresh rate of
|
||||
previewed animations.
|
||||
|
||||
See \l {Optimizing Your 3D Scene} to learn how you can enhance the
|
||||
performance by optimizing your scene.
|
||||
|
||||
\section1 FAQ - Data Simulation
|
||||
|
||||
\section2 Can I automatically generate dummy data?
|
||||
No, this is not supported at the moment. For more information about creating
|
||||
the data manually, see \l {Loading Placeholder Data}.
|
||||
*/
|
||||
|
Reference in New Issue
Block a user