Am 24.10.24 um 16:32 schrieb Ivan Solovev via Development:
Hi,
following up on the Deprecation vs Compatibility discussion from
the Qt Contributor Summit [0], I implemented a macro that allows to mark
the APIs as deprecated and to-be-removed in the Next Major Release [1].
[0]:https://wiki.qt.io
On 08.09.24 3:25 PM, 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 to the problem being
access to the Sentry dashboard
would also be nice.
I'd have to check with Harald who is driving Sentry on our side, but we
should be able to arrange something useful.
Cheers,
Tor Arne
On Sep 8, 2024, at 3:25 PM, Nicolas Fella via
Development wrote:
Hi,
at Akademy I had a c
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 to the problem being in
Qt instead of in KDE code. In those cases we of course wa
properties, so that types actually stay intact.
On 10.05.24 16:18, Nicolas Fella via Development wrote:
Hi,
one of the documented limitations of qmlcachegen is that it cannot
properly compile code that is using Qt Quick Controls. The
recommendation here is to specify a style at compile
Hi,
one of the documented limitations of qmlcachegen is that it cannot
properly compile code that is using Qt Quick Controls. The
recommendation here is to specify a style at compile time by directly
importing it. This recommendation may be fine for some projects, but for
us in KDE it poses a pro
Hi,
after updating my local Qt 6.7 + KDE build I noticed a number of severe
UI bugs in various QML-based programs (Plasma, System Settings, several
applications) where certain elements are wrongly sized. Investigating
lead me to https://bugreports.qt.io/browse/QTBUG-117597, which suggests
to me t
