On Sun, 8 Sept 2024 at 16:27, Nicolas Fella via Development
wrote:
>
> Hi,
>
> at Akademy I had a chat with Volker Hilsheimer and now want to open this
> to a wider audience.
>
> In KDE we have an automatic crash reporting system based on Sentry.
> Naturally some amount of the crash reports point
Hi!
We have branched '6.8.0' from '6.8' now. So from now on all changes targeted to
Qt 6.8.0 release must have 'Pick-to: 6.8.0' and '6.8' is for Qt 6.8.1. But
remember, please do not try to add anything nice-to-haves in '6.8.0' anymore;
we will take in only fixes for release blockers (+ of co
Qt 6.7 status
* Branching from '6.7' to '6.7.3' is done
* Target is to release Qt 6.7.3 Thu 19th September
* Qt 6.7.3 will be the last release from Qt 6.7 series
Qt 6.8 status
* Qt 6.8 Beta4 is released
* Qt 6.8 API review is done
* Qt 6.8 RC preparations are ongoing
On Tuesday 10 September 2024 10:33:32 GMT-7 Thiago Macieira wrote:
> Is this supported? I didn't know about it until yesterday. I doubt anyone is
> using it, though it's possible some code carried over from Qt 3 was left
> unmodified like that.
QGroupBox:
Q_PROPERTY(Qt::Alignment alignment RE
On Monday 9 September 2024 12:09:44 GMT-7 Christian Ehrlicher via
Development
wrote:
I try to get in some provisioning scripts into qt5.git but it constantly
fails in tst_moc for windows-11_23H2-minimal-static with a timeout.
QtBase points to aec8398d71d351e956683a695af51317fe65097e from start o
On Tuesday 10 September 2024 10:12:10 GMT-7 Andreas Aardal Hanssen wrote:
> Tir 10 sep 2024 kl. 18:55 skrev Thiago Macieira:
> > Any objections?
>
> Please don’t break source compatibility?
It does appear that a Q_PROPERTY of a Q_FLAG whose getter and setter operate
on integers still compiles, b
On Tuesday 10 September 2024 09:55:24 GMT-7 Thiago Macieira wrote:
> 1) I will fix moc to *not* manipulate int for property enum types, which
> means it will not use QFlag at all
https://codereview.qt-project.org/c/qt/qtbase/+/589897
If we need to keep compatibility with integer getters and sette
Tir 10 sep 2024 kl. 18:55 skrev Thiago Macieira:
> Any objections?
Please don’t break source compatibility?
Andreas 😊--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On Tuesday 10 September 2024 06:08:34 GMT-7 Eirik Aavitsland via Development
wrote:
> > Thank you Aavit. Did already QFlags have the enum_type typedef in this
> > commit?
> >
> > Another question: did QVariant in this commit already have userType()?
>
> You're welcome, Thiago!
> No enum_type or
On 9/10/24 13:56, Thiago Macieira wrote:
On Monday 9 September 2024 23:00:28 GMT-7 Eirik Aavitsland via Development
wrote:
No idea if this is helpful, but it seems that what was later renamed
QFlag was introduced as QFlagInternal in this commit:
Thank you Aavit. Did already QFlags have the enu
On Tuesday 10 September 2024 04:56:40 GMT-7 Thiago Macieira wrote:
> In Qt 3, QVariant could only contain a closed set of types, so QObject::
> QObject::setProperty would only be able to write QFlags if the QVariant
> contained an int, and QMetaProperty already had isEnumType() at this time
> htt
On Monday 9 September 2024 23:00:28 GMT-7 Eirik Aavitsland via Development
wrote:
> No idea if this is helpful, but it seems that what was later renamed
> QFlag was introduced as QFlagInternal in this commit:
Thank you Aavit. Did already QFlags have the enum_type typedef in this commit?
What I f
12 matches
Mail list logo
