Re: [Development] QMetaType and type aliases for primitive types

2021-05-08 Thread Alberto Mardegan
Hi Tiago, On 08/05/21 18:47, Thiago Macieira wrote: > And the problem is that they *do* depend on the CPU architecture. long > changes > size depending on OS and pointer size. yes, I knew that long changes size depending on the architecture, but: > As far as I am concerned, the fact that > in

Re: [Development] QMetaType support for QFuture

2021-05-08 Thread Konstantin Ritt
Can't we simply `QFutureInterface(const QFuture &future)` to get that future's QFutureInterface, w/o any QtPrivate:: ugliness? Regards, Konstantin сб, 8 мая 2021 г. в 11:30, Sona Kurazyan : > Hi Konstantin, > > > > QFuture has a constructor for QFuture from QFuture, see > https://code.qt.io/c

Re: [Development] QMetaType and type aliases for primitive types

2021-05-08 Thread Thiago Macieira
On Saturday, 8 May 2021 00:48:51 PDT Alberto Mardegan wrote: > Hi there! > I'm struggling to understand what's going on with types being > marshalled onto D-Bus, and I'd like to understand if what I'm seeing is > a but with the Qt version I'm using (Qt 5.12.7 + some patches), an issue > with the

Re: [Development] QMetaType support for QFuture

2021-05-08 Thread Sona Kurazyan
Hi Konstantin, QFuture has a constructor for QFuture from QFuture, see https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/thread/qfuture.h#n82, so you don’t even need to use the broken qToVoidFuture() method. I’ll probably remove it, since it was always broken and couldn’t be ever used. I

Re: [Development] QMetaType support for QFuture

2021-05-08 Thread Sona Kurazyan
I see the problem. I guess adding an internal API in QtCore (likely in QtPrivate namespace), which is a friend to QFuture and gives access to its d-ptr is the only option then. At least I cannot think of a better way. Best regards, Sona > -Original Message- > From: Arno Rehn > Sent: Fr

Re: [Development] QMetaType and type aliases for primitive types

2021-05-08 Thread Alberto Mardegan
On 08/05/21 10:48, Alberto Mardegan wrote: > Interestingly, I'm seeing this on amd64 only; it seems that on armhf > everything is working fine. Could it be a bug with the compiler? In armhf, QMetaType::type("int64_t") always returns 4 (LongLong), even before registering the metatype (maybe this st

[Development] QMetaType and type aliases for primitive types

2021-05-08 Thread Alberto Mardegan
Hi there! I'm struggling to understand what's going on with types being marshalled onto D-Bus, and I'd like to understand if what I'm seeing is a but with the Qt version I'm using (Qt 5.12.7 + some patches), an issue with the compiler, or just the expected behaviour. The problem is that QtDBus f