2014-04-24 22:42 GMT+02:00 Dominik Holland :
>
> I like that idea, but couldn't we do something like this ?
>
> qRegisterWrapper(qMetaTypeId())
>
> MyWrapper is a QObject based class which can whatever you want and gets
> YourType as reference or per value.
>
> It would mean you create your wrappe
>
>
>
> >>> While your proposed approach is rather clean, it carries one drawback,
> >>> which is the lack of type information, with all its consequences.
>
PRO:
*- Can data-clean/input-validate on either C++ or QML side, can add more
custom validators in different places
*- ?More fine-grain
On Friday 25 of April 2014 13:03:33 Richard Moore wrote:
> On 25 April 2014 11:51, Alberto Mardegan wrote:
> > For instance, I would like to have a GeoPoint type with "latitude" and
> > "longitude" properties; if I exposed it as a QVariantMap, I wouldn't be
> > able to prevent the QML code from doi
On Apr 25, 2014, at 7:28 AM, Dominik Holland
wrote:
>
> Am 25.04.14 15:05, schrieb Joshua Kolden:
>>
>> On Apr 25, 2014, at 3:51 AM, Alberto Mardegan
>> wrote:
>>
>>> On 04/24/2014 03:11 PM, Joshua Kolden wrote:
>>> [...]
We have a solution that works very well for us using QVariantMa
Am 25.04.14 15:05, schrieb Joshua Kolden:
>
> On Apr 25, 2014, at 3:51 AM, Alberto Mardegan
> wrote:
>
>> On 04/24/2014 03:11 PM, Joshua Kolden wrote:
>> [...]
>>> We have a solution that works very well for us using QVariantMaps and an
>>> MVC pattern / strong separation between data objects an
On Apr 25, 2014, at 3:51 AM, Alberto Mardegan
wrote:
> On 04/24/2014 03:11 PM, Joshua Kolden wrote:
> [...]
>> We have a solution that works very well for us using QVariantMaps and an
>> MVC pattern / strong separation between data objects and view. It
>> appears to me that most people are ha
On 25 April 2014 11:51, Alberto Mardegan wrote:
> For instance, I would like to have a GeoPoint type with "latitude" and
> "longitude" properties; if I exposed it as a QVariantMap, I wouldn't be
> able to prevent the QML code from doing stuff like:
> p.latitude = 60
> p.longitde = 10 // note the t
On 04/24/2014 03:11 PM, Joshua Kolden wrote:
[...]
> We have a solution that works very well for us using QVariantMaps and an
> MVC pattern / strong separation between data objects and view. It
> appears to me that most people are having this issue because it’s not
> common to use MVC with QtWidge
Am 24.04.14 12:46, schrieb Simon Hausmann:
> On Thursday 24. April 2014 11.55.07 Roland Winklmeier wrote:
>> Hi list,
>>
>> we discussed the topic whether non-QObject types can be used in QML or not
>> several times. The last time is only a few days ago as part of the Qt
>> future discussions. So
I’m sorry I intended to respond to this in the other thread, but super busy.
Nevertheless I think it’s important for people to know there are answers to
this now without waiting for any new APIs so I stole the time to write our
process out.
We have a solution that works very well for us using
On Thursday 24. April 2014 11.55.07 Roland Winklmeier wrote:
> Hi list,
>
> we discussed the topic whether non-QObject types can be used in QML or not
> several times. The last time is only a few days ago as part of the Qt
> future discussions. So I had some thoughts what needs to happen to solve
Hi list,
we discussed the topic whether non-QObject types can be used in QML or not
several times. The last time is only a few days ago as part of the Qt
future discussions. So I had some thoughts what needs to happen to solve
this issue.
I can remember someone told me there are plans to add such
12 matches
Mail list logo
