<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with qgadget]]></title><description><![CDATA[A list of topics that have been tagged with qgadget]]></description><link>https://forum.qt.io/tags/qgadget</link><generator>RSS for Node</generator><lastBuildDate>Thu, 20 Aug 2026 18:09:13 GMT</lastBuildDate><atom:link href="https://forum.qt.io/tags/qgadget.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[Custom type with typedef&#x27;s in QML]]></title><description><![CDATA[I have found partial "solution":

QML can not correctly work with quint8 when it was typedefed and qRegistered. Changing initial type to quint32 solved the issue when QML can not correctly display its value.
Passing Q_GADGET to QML via model's method data with using QVariant as a "transport" type works incorrectly (Q_GADGET inner variables cannot be changed for some reason), but passing it directly with separate model's method as

Example getExpample(int index);

works well. Anyway copying the Example's object in the both cases works well, but the last one allows to modify Example's members in QML.
I can not say that my issue was solved (now I'm going to use quint32 and the second approach to pass Q_GADGET copy to QML), but I'm wondering, if this is a correct QML/QVariant/Q_GADGET behaviour to avoid such issues further.
]]></description><link>https://forum.qt.io/topic/129337/custom-type-with-typedef-s-in-qml</link><guid isPermaLink="true">https://forum.qt.io/topic/129337/custom-type-with-typedef-s-in-qml</guid><dc:creator><![CDATA[St.Stanislav]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>