aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLeena Miettinen <riitta-leena.miettinen@qt.io>2021-03-25 09:50:46 +0100
committerLeena Miettinen <riitta-leena.miettinen@qt.io>2021-03-26 10:44:45 +0000
commitc79df73bde5c1e416e3cfd2d16f16ff607d8d5b8 (patch)
tree749054997ba376f2c6b6f453d3d5ca5d70f9ef52
parentd3faab0e725e2fcc38b0ce22a24bd62726807f47 (diff)
Doc: Add info on exporting nested Figma component instances
Fixes: QDS-4049 Change-Id: Ia5f370bab2d44fc90ded48ddc8b089bc9975d921 Reviewed-by: Vikas Pachdha <vikas.pachdha@qt.io>
-rw-r--r--doc/qtdesignstudio/src/qtbridge/qtbridge-figma-using.qdoc5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/qtdesignstudio/src/qtbridge/qtbridge-figma-using.qdoc b/doc/qtdesignstudio/src/qtbridge/qtbridge-figma-using.qdoc
index c703074b95..98817db6a9 100644
--- a/doc/qtdesignstudio/src/qtbridge/qtbridge-figma-using.qdoc
+++ b/doc/qtdesignstudio/src/qtbridge/qtbridge-figma-using.qdoc
@@ -57,6 +57,11 @@
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.
+ 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.
\li Use descriptive and unique IDs to avoid duplicate IDs after
exporting designs and importing them to \QDS.
\endlist