Re: [Development] Nominating David Redondo for approval status

+1! Am 01.02.24 um 15:10 schrieb David Edmundson: I would like to nominate David Redondo for approver rights in the Qt project. David's first contributions to Qt started in November 2020, but has ramped up this last year working on the Qt Wayland platform. Not only has he fixed a lot of issues

Re: [Development] Nominating Vlad Zahorodnii for approval status

+1! Am 01.02.24 um 15:11 schrieb David Edmundson: I would like to nominate Vlad Zahorodnii for approver rights in the Qt project. Vlad has also been working on the QtWayland backend, providing insight based on his other role as one of the kwin maintainers. Vlad and I have been working together

Re: [Development] Request for early MOC support for C++20 Modules

Hi, > On a related note, when moving a class to modules, it would be handy to > have a way to skip the 'Generate Missing Q_PROPERTY Members' boilerplate > code. My current classes are mostly 50% getter/setter boilerplate, and > in my opinion, this is only manageable because we split our code

Re: [Development] Replacement for QFont::ForceIntegerMetrics in Qt 6?

Hi, thanks, QFont::PreferFullHinting seems to do the trick. I actually had that set for testing and thought QTextOption::setDesignMetrics(false) was the fix (after reading a bit of QFontEngineFT) but it was the hinting all along :-) Thanks! Cheers Kai Uwe Am 06.11.23 um 12:04 schrieb

[Development] Replacement for QFont::ForceIntegerMetrics in Qt 6?

Hi everyone, in Qt 5.15 the QFont::ForceIntegerMetrics was deprecated and subsequently removed in Qt 6. The rendering engine in Konsole, KDE’s terminal emulator, relies on the fact that every glyph in the monospace font is rendered at the same width, since sections of different style (e.g.

Re: [Development] QSGText: Why round glyph position like this?

Hi, thanks for your insights, Eskil! I am running a self-compiled Qt dev, so it’s all up-to-date. I did some further investigation and found that the glyph cache is actually rendered alright, so nothing to do with FreeType etc. It seems that the textmask.vert [1] shader is still not

[Development] QSGText: Why round glyph position like this?

Hi everyone, while investigating blurry font with native renderer in QML apps in Plasma 6 under Wayland with fractional scaling (devicePixelRatio 1.75 in my case), I stumbled upon QSGTextMaskMaterial::populate which rounds the glyph position [1] citing Mac OS behavior. When I remove the

Re: [Development] QtQuick Dialogs Widgets fallback

Hi, Which style are you referring to here? The default QML one, none Fusion/Material/etc substyles. If there's a way we can improve our desktop-based fallbacks, it would be good to know about that. First of all, they suffer from the same issue as most of QtQuick Controls 2, being in the

[Development] QtQuick Dialogs Widgets fallback

Hi everyone, we found that the Qt Quick Dialogs (MessageDialog and friends) do not support a fallback to their widget counterpart like the ones from Qt.labs.platform did. In KDE Plasma we do not provide a platform theme implementation for the message or color dialogs, as the Qt ones are

Re: [Development] Using DMA instead of SHM in non OpenGL apps (Linux/Wayland)

Hi, Qt Wayland Client currently relies on EGL through wayland-egl integration to do the right thing. On Mesa for instance Qt indeed transparently uses zwp_linux_dmabuf_v1. However, I agree that Qt itself should have an implementation of the aforementioned protocol on the *client* side, too

Re: [Development] std::optional for Q_PROPERTY

Hi, > That would mostly work, unless you want > a RESETable property, where RESET shouldn't lead to a nullopt value. It’s perfectly valid to have RESET set the value to whatever it thinks is correct, isn’t it? All it means is I can assign `undefined` from QML and have _something_ come out of

[Development] std::optional for Q_PROPERTY

Hi everyone, something that came up during this year’s KDE Akademy was that we believe Q_PROPERTY should be able to handle std::optional, such that you get a null QVariant out of it if it has no value. The main use case being interfacing “more modern C++” with QML in a type-safe way, rather

Re: [Development] QKeySequenceEdit: Unable to assign tab

Hi, you cannot reply rely on RTTI in Qt Core. static_cast is fine in this scenario as we know it'll be a key event. Cheers Kai Uwe ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development

Re: [Development] Proposal to deprecate the amazing QApplication::globalStrut

Hi, Am 05.12.19 um 14:25 schrieb Shawn Rutledge: So I’m tempted to think that we could try to extend QPalette to store other data types in addition to colors, but it doesn’t look possible to maintain existing API or implementation enough to be worthwhile; and it would tend to become too much

Re: [Development] QTCS2019 Notes from QtQml session

Hi, > these are the notes on the QtQml session: > Versioning > -- > > Once we get rid of unqualified lookups we don't need any QML versioning > anymore. At least the minor version will become optional already in 5.15 > for well-behaved QML documents. In QML 3 it won't be allowed. While