Commit 488f2454 authored by Leena Miettinen's avatar Leena Miettinen
Browse files

Doc: Explain that property editor cannot handle custom class properties


That is, Q_PROPERTY types for custom types that have been declared
with Q_DECLARE_METATYPE().

Fixes: QTBUG-17816
Change-Id: I48c33af13d85b877596caca4fbd1103bf383d6e8
Reviewed-by: default avatarFriedemann Kleint <Friedemann.Kleint@qt.io>
parent 4d417394
No related merge requests found
Showing with 18 additions and 11 deletions
......@@ -68,17 +68,24 @@
also provides an interface for creating custom property sheet
extensions.
\warning \QD uses the QDesignerPropertySheetExtension to feed its
property editor. Whenever a widget is selected in its workspace,
\QD will query for the widget's property sheet extension. If the
selected widget has an implemented property sheet extension, this
extension will override the default property sheet.
\warning The data types used by the property sheet for some properties
are opaque custom QVariant types containing additional information
instead of plain Qt data types.
For example, this is the case for enumerations, flags,
icons, pixmaps and strings.
Keep the following limitations in mind:
\list
\li \QD uses the QDesignerPropertySheetExtension to feed its
property editor. Whenever a widget is selected in its workspace,
\QD will query for the widget's property sheet extension. If the
selected widget has an implemented property sheet extension, this
extension will override the default property sheet.
\li The data types used by the property sheet for some properties
are opaque custom QVariant types containing additional information
instead of plain Qt data types. For example, this is the case for
enumerations, flags, icons, pixmaps and strings.
\li \QD's property editor has no implementation for handling
Q_PROPERTY types for custom types that have been declared
with Q_DECLARE_METATYPE().
\endlist
To create a property sheet extension, your extension class must
inherit from both QObject and
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment