QtDesignStudio/FAQ: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
(First FAQ entry with correct structure of table of contents)
Line 9: Line 9:


==Design Studio & MCU==
==Design Studio & MCU==
===What are the main differences between Qt Quick and Qt Ultralite?===
There are several differences that result from optimizations needed for the embedded world. These include:
* Some QML types are unavailable in Qt Ultralite. The available types are listed [https://doc.qt.io/QtForMCUs-2.8/qtul-qmltypes.html here].
* Some of the types have additional constraints what is described [https://doc.qt.io/QtForMCUs-2.8/qtul-known-issues.html here].
* The QML/JS support is limited for MCU to the features described [https://doc.qt.io/QtForMCUs-2.8/qtul-javascript-environment.html here].
For full overview of the differences please refer to [https://doc.qt.io/QtForMCUs-2.8/qtul-qtquick-differences.html QtForMCUs docs].


==Qt Bridge for Figma export==
==Qt Bridge for Figma export==

Revision as of 12:19, 25 September 2024

En Ar Bg De El Es Fa Fi Fr Hi Hu It Ja Kn Ko Ms Nl Pl Pt Ru Sq Th Tr Uk Zh

This page contains technical FAQs for Design Studio, its MCU support as well as Figma integration.

Design Studio & MCU

What are the main differences between Qt Quick and Qt Ultralite?

There are several differences that result from optimizations needed for the embedded world. These include:

  • Some QML types are unavailable in Qt Ultralite. The available types are listed here.
  • Some of the types have additional constraints what is described here.
  • The QML/JS support is limited for MCU to the features described here.

For full overview of the differences please refer to QtForMCUs docs.

Qt Bridge for Figma export

Design Studio import of data from Qt Bridge for Figma

Lorem Ipsum1?

Lorem Ipsum

Lorem Ipsum2?

Lorem Ipsum

Lorem Ipsum3?

Lorem Ipsum