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

Doc: Describe detaching changed Figma component instances before export

Browse Source 
Task-number: QDS-3338
Change-Id: I86e7c057a2e97ecd30b84e6f4b52d230fda80c5f
Reviewed-by: <kama.wojcik@qt.io>
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
This commit is contained in:
Leena Miettinen
2021-03-29 16:59:28 +02:00
parent 33359883f2
commit d1228a6f39
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
doc/qtdesignstudio/src/qtbridge/qtbridge-figma-using.qdoc
View File

@@ -57,11 +57,14 @@
as assets. If you use functional \QDS components in Figma, you will
find it easier to merge new iterations of the design to \QDS and
continue to build the screens there.
\li If your Figma components contain nested components, Figma allows
you to hot swap the nested instance inside the component instance.
\li \QBF does not support exporting changes in component instances.
If you make changes to component instances in Figma, you must
detach the instances before exporting them. Similarly, if your
Figma components contain nested components, Figma allows you to
hot swap the nested instance inside the component instance.
However, \QBF doesn't support this so you get the original
component instead. If you want to make further changes to a
component, detach component instances from it before exporting it.
component unless you detach the component instance before
exporting it.
\li Use descriptive and unique IDs to avoid duplicate IDs after
exporting designs and importing them to \QDS.
\endlist