Re: [Interest] Embedded Font in PDF

The PDF font embedding is something that I’ve implemented quite a few years ago, and I believe the code has been mostly unchanged since then. The reason it doesn’t look quite as many tools might expect it to has to do with how Qt uses a ‘virtual’ font to render text that can consist of a list

Re: [Interest] L Word

Hi all, After being notified about this whole mess yesterday evening, I’ve now spent quite a bit of time to catch up on the whole thread. The purpose of this mailing list is for users to help each other and discuss Qt related topics. The whole thread of postings leading to this is in that

Re: [Interest] How to create read-only bindable properties?

On 13 Dec 2020, at 14:22, Alexey Rochev mailto:equ...@gmail.com>> wrote: I want to create bindable property that can be used in other properties' bindings, but which can be modified (and to which bindings can be set) only from inside of an object that owns it. With Qt5 and signals, you would do

Re: [Interest] Qt 6.0 and the future of QWebSockets module

Hi, The plan is to bring those modules back after Qt 6.0. This is mainly a prioritisation question right now, where the choice was to focus most development efforts on the Qt Essentials to make them as good as possible for Qt 6. So I expect that we’ll have a fully supported web sockets module

Re: [Interest] macOS Big Sur ARM Build

Hi, We’ll certainly support Big Sur, but the amount of work we need to do there to make things work 100% is yet unknown as well, especially as Apple has made rather large changes to their look and feel. Regarding macOS/ARM I don’t see a huge problem for Qt. Short term, Rosetta2 should have us

Re: [Interest] Change in open-source licensing of Qt Wayland Compositor, Qt Application Manager and Qt PDF

Hi, As it turned out, there was some miscommunication that happened regarding the re-licensing of Qt PDF, and not all contributors were on board regarding the license change. That means we’re not changing the modules license and won’t be adding it to become a supported part of Qt until this

Re: [Interest] Chasing a standard

> On 4 Nov 2018, at 22:13, Roland Hughes wrote: > > Quoting Elvis Stansvik: > > > Sorry to say it, but welcome to C++ > > No, mostly kidding. I think what you suggest sort of makes sense. If > Qt are to keep its containers, with a goal of offering an alternative > more

Re: [Interest] Backporting bugs to Qt 5.6

On 24 Sep 2018, at 14:11, Danny Smit mailto:danny.smi...@gmail.com>> wrote: On Fri, Sep 21, 2018 at 11:11 AM Alexandru Croitor mailto:alexandru.croi...@qt.io>> wrote: You will probably want to read http://wiki.qt.io/Qt_Contribution_Guidelines And specifically to your questions, bug fixes

Re: [Interest] Future of Qt [was: Future of Qt3d]

> On 8 Nov 2017, at 11:54, Alexander Ivash wrote: > > This is really confusing. > > From one side, > >>> What you **don't** say is, that you "genuinely wish to treat the Qt >>> Project as an Open Governance project and that external contributions >>> are welcomed and

Re: [Interest] Future of Qt [was: Future of Qt3d]

> On 8 Nov 2017, at 09:09, Thiago Macieira wrote: > > On Tuesday, 7 November 2017 18:17:30 PST m...@herrdiel.de wrote: >> --> You say that KDAB contributed much work and that you: "[...] hope to >> have KDAB back contributing", but you also state, that they are not >>