Il 05/02/19 18:16, Dmitriy Purgin ha scritto:
I couldn't figure out the exact combination but as far as I remember, if
you have namespaced code, you have to always fully qualify the enum
class parameters in signals and slots.
This is actually also the case for enums and enum classes. For
On Tuesday, 5 February 2019 10:46:45 PST Matthew Woehlke wrote:
> On that note, will uic in Qt6 finally use the new PMF syntax?
We can add this mode right now.
It won't replace the connectSlotsByName() feature, of course, since that is
entirely based on runtime (it depends on the object name).
On 05/02/2019 11.58, Thiago Macieira wrote:
> On Tuesday, 5 February 2019 08:43:03 PST Jason H wrote:
>> Should all new connections be in the modern syntax?
>
> Yes, if you can.
On that note, will uic in Qt6 finally use the new PMF syntax?
--
Matthew
Hi Jason,
in one of the projects with Qt 5.9 I used enum classes in signals and slots
and it worked fine, even with the new Q_NAMESPACE thing. One thing though:
I couldn't figure out the exact combination but as far as I remember, if
you have namespaced code, you have to always fully qualify the
> Sent: Tuesday, February 05, 2019 at 11:58 AM
> From: "Thiago Macieira"
> To: development@qt-project.org
> Subject: Re: [Development] Enum classes in signals?
>
> On Tuesday, 5 February 2019 08:43:03 PST Jason H wrote:
> > While I prefer enum classes myself, I just had to connect to a signal
On Tuesday, 5 February 2019 08:43:03 PST Jason H wrote:
> While I prefer enum classes myself, I just had to connect to a signal with
> one in it. This was unfortunate as I was attempting to use the old
> connection syntax SIGNAL()/SLOT() macros. I was not aware that the old
> syntax were being
Is it really deprecated? Didn’t find any notice and wonder how it could get
deprecated as the f-ptr syntax is not functionally equivalent to the macro
syntax.
Beste Grüße / Best regards,
Alexander Nassian
> Am 05.02.2019 um 17:43 schrieb Jason H :
>
> While I prefer enum classes myself, I
While I prefer enum classes myself, I just had to connect to a signal with one
in it. This was unfortunate as I was attempting to use the old connection
syntax SIGNAL()/SLOT() macros. I was not aware that the old syntax were being
deprecated? What is the policy on this?
Should signals not use
Hi, all!
I have finally published my HDR patchset in gerrit! It was the first time I
pushed something into gerrit, so if I did something wrongly, please tell :)
https://codereview.qt-project.org/#/c/252187/
There are a few general questions I would like to ask your opinion about:
1) Is it okay
Can we remove a platform in a minor version?
Best regards,
Jesús
Original message
From: Harald Kjølberg
Date: 05/02/2019 15:56 (GMT+01:00)
To: development@qt-project.org
Subject: Re: [Development] Intention of dropping UWP 2015 x86 builds in favour
of MinGW 32-bit packages
Hi,
As no objections have been received, the proposed change will be implemented,
effective from Qt 5.12.2.
Cheers,
Harald
From: Development on behalf of Harald
Kjølberg
Date: Tuesday, 22 January 2019 at 14:36
To: "development@qt-project.org"
Subject: [Development] Intention of dropping
Hey everyone,
I noticed that since the upgrade to 5.12.1 the following include option is
added to my projects compiler flags: "-IC:\VulkanSDK\1.0.51.0\include"
It seems to origin from
"modules/qt_lib_gui_private.pri:QMAKE_INCDIR_VULKAN".
It does not do any harm to my build, but I wonder if that
12 matches
Mail list logo