Hi everyone,
Also a Qt3D user here, and I would like to echo Harald’s sentiments– and a big
thanks to Harald for saying my thoughts out loud.
I had already privately tried to communicate my thoughts to Tuukka on this
subject, but here is my public take…
As the Qt champion inside my
Hi Mike,
You're absolutely right, somehow I missed that... 6.4.1 renderer appears to
work again, once 6.4.2 fixes the font issues I'll give it a thorough test.
Thanks!
Mark
-Original Message-
From: Mike Krus
Sent: 30 November 2022 11:24
To: Mark De Wit
Cc: development@qt
Dear Qt devs,
I have a Qt 3D application that relies on the RHI render plugin, and is stuck
on Qt 6.1.x due to the GPL licensing issue for Qt6ShaderTools.dll.
Now that Qt6ShaderTools has been relicensed to LGPL in June of this year, will
the RHI render plugin be re-instated in the default
ownership and destruction, generating all the necessary template
instances, etc. Of course no modern solution would follow the SWIG approach of
writing your own C++ parser, but for what it is, it works pretty well.
Mark
From: samuel ammonius
Sent: 12 September 2022 21:44
To: Mark De Wit ; development
This sounds like QPyBind11 to me?
Mark
-Original Message-
From: Development On Behalf Of Cristián
Maureira-Fredes
Sent: 31 August 2022 23:33
To: development@qt-project.org
Subject: [EXTERNAL EMAIL] Re: [Development] Repository request:
playground/qtscrypt
On 8/31/22 21:33, Konrad
Note, I've been informed on that bug that shared and static builds require
different fixes and therefore created a new bug report QTBUG-94066 for fixing
the shared / official installs versions.
Thank,
Mark
From: Development On Behalf Of Mark De Wit
Sent: 27 May 2021 17:50
To: Development@qt
I'd like to flag up bug report https://bugreports.qt.io/browse/QTBUG-89643
which is closed as fixed in Qt 6.1.0 but is still (or again) broken in Qt 6.1.1
I added a comment to the Bug, but in my testing, the Qt6 Gui module does not
load its plugin as part of its cmake processing, and CMake thus
> From: Development On Behalf Of
> Morten Sørvig
> Sent: 18 February 2020 13:38
> To: Qt development mailing list
> Subject: Re: [Development] Qt 5.13 & 5.14 add device-independent pixels to
> device-dependent
>
> > On 14 Feb 2020, at 21:46, Thiago Macieira
> wrote:
> >
> > On Friday, 14
> From: Development On Behalf Of Sze
> Howe Koh
>
> Another use case: Mass deployment to multiple PCs:
> https://forum.qt.io/topic/111587/classroom-deployment-of-qt-for-multiple-
> pcs-and-for-all-users-windows
>
This mass-deployment is the use case that concerns me most of all. I have 45
> Edward Welbourne
> > Alexander Akulich (6 February 2020 16:33) asked:
> > Are we going to provide some Qt5 → Qt6 migration tool?
>
> https://codereview.qt-project.org/c/qt/qtrepotools/+/289121
>
> > It is trivial to grep the sources for
> > "SIGNAL(error(QAbstractSocket::SocketError))" and
: Tino Pyssysalo
> Sent: 31 January 2020 09:32
> To: Mark De Wit ; Qt development mailing list
>
> Subject: Re: [Development] Changes to Qt offering
>
> The problem must be somewhere else. There are no installer changes in
> production yet.
> --
> Tino Pyssy
developers in this company to
create Qt accounts, that's a non-starter...
Mark
> -Original Message-
> From: Development On Behalf Of
> Mark De Wit
> Sent: 28 January 2020 11:38
> To: Lars Knoll ; Qt development mailing list
>
> Subject: Re: [Development] C
I've been working really hard over the past few years to get Qt used more
within my organisation. However, mandating that our 45 developers all register
Qt accounts is a complete non-starter, especially if only 2 or 3 of them
actually work with UI on a day-to-day basis. For the rest of them,
Is there a chance that the high-dpi work will fix the dpi-awareness of the
Fusion theme as reported in https://bugreports.qt.io/browse/QTBUG-74100 ?
Last time I checked there was a fair amount of drawing code that didn't check
what screen a widget was on, and hence used "global" scaling (if
> -Original Message-
> From: Development On Behalf Of
> Konstantin Tokarev
> Sent: 06 June 2019 14:30
> To: Simon Hausmann ; Bogdan Vatra
> ; development@qt-project.org
> Subject: Re: [Development] Proposing CMake as build tool for Qt 6
>
>
>
> 06.06.2019, 16:25, "Simon Hausmann" :
> >
> From: Development On Behalf Of
> Thiago Macieira
> > On Tuesday, 9 April 2019 05:11:03 PDT Pouya Shahinfar wrote:
> > You open a project which is developed by someone else, and he/she used
> > QDateTime for holding time and date. The problem here is you as a
> > newcomer to project do not know
Interesting find - that fix might have solved my issue with Fusion theme as
well. From the looks of it, QWindow* support was added to some theme code
since that bug report, but not consistently for all controls and all themes.
It would have been great to fix this at the QIcon level rather
Are you using Fusion theme by any chance? I'm facing the same issue, I even
tried writing my own Icon Engine to try and improve matters, but turns out
widgets are simply requesting the wrong size icon - nothing the icon engine can
do to "second-guess" such requests...
I have filed one such
I’ve had a good experience adding KPlotWidget into my application for simple
line plots. It’s simple and easily to modify if required.
https://github.com/KDE/kplotting
Mark
From: Development On Behalf Of Denis
Shienkov
Sent: 23 March 2019 07:57
To: Alexander Nassian
Cc:
alpha for
another data point.
Mark
-Original Message-
From: Jani Heikkinen
Sent: 01 February 2019 09:53
To: Mark De Wit ; development@qt-project.org
Subject: Re: [Development] HEADS-UP: Branching from '5.12' to '5.12.1' started
Hi!
This is sadly to hear. Please report all findings
-Original Message-
From: Development On Behalf Of Mark De Wit
Sent: 30 January 2019 11:45
To: development@qt-project.org
Subject: Re: [Development] HEADS-UP: Branching from '5.12' to '5.12.1' started
Good point. I only just now saw & read the entire tooltip for WebEngine.
I a
Subject: Re: [Development] HEADS-UP: Branching from '5.12' to '5.12.1' started
This suggestion is already in JIRA see
https://bugreports.qt.io/browse/QTBUG-71579
Br
Michal
On 01/30/2019 11:29 AM, Kai Koehne wrote:
>> -Original Message-
>> From: Development On Behalf Of
>>
Selecting MSVC 2015 64-bit + Qt WebEngine for 5.12.1 in the installer does not
give me WebEngine. Is that intentional? Should the installer perhaps warn
that the selected combination is unsupported?
I shall try again with MSVC 2017...
KR,
Mark
-Original Message-
From: Development
It's great to see a resolution so close... I'll see if I can find time to try
the patch locally.
Really appreciate the work going into it!
Kind regards,
Mark
-Original Message-
From: Michal Klocek
Sent: 17 October 2018 09:32
To: Mark De Wit ; development@qt-project.org
Subject: Re
What is the criteria for blocker? It would be great if WebEngine were usable
again for people behind proxies (my last usable Qt release is 5.9)...
https://bugreports.qt.io/browse/QTBUG-69281 is marked as P1 but not targeted
at 5.12?
Kind regards,
Mark
-Original Message-
From:
A qt.conf file could also help point to correct locations. It doesn't have to
be absolute, it can be relative? This is how we deal with the hard-coded paths.
Mark
-Original Message-
From: Development On
Behalf Of Thiago Macieira
Sent: 28 June 2018 15:58
To:
I have an application based on qt-solutions qtwinmigrate sample.
Because we're integrating Qt into an existing MFC application, we're not even
running QApplication exec. The application uses MFC's entry point for startup
and drives the Qt event loop manually as part of the MFC event loop.
7:43
To: development@qt-project.org
Subject: Re: [Development] -developer-build (was: [5.7-beta] compile error with
xcode-6.4
On quarta-feira, 4 de maio de 2016 07:46:41 PDT Mark De Wit wrote:
> The configure flags are poorly documented, and options like qtlibinfix
> (which I understood to be a recomm
Having tried to do this myself last week, I cannot find any "official"
documentation on how to build Qt myself for an official release with our
software. Doing our own build has proven frustrating enough that we abandoned
the current attempt to update our version of Qt.
The configure flags
Keep in mind that from Windows 8.1 onwards, DPI can be set per-screen (I myself
have a 4K screen (240 dpi, 250% scaling) + regular HD screen (120 dpi, 125%
scaling)). Qt appears to already handle the appropriate new dpi-aware APIs (Qt
defaults to per-monitor DPI aware on Windows 8.1+).
Sadly,
transform to make them scale to 250%.
Mark
-Original Message-
From: Development [mailto:development-boun...@qt-project.org] On Behalf Of
Thiago Macieira
Sent: 29 December 2015 12:19
To: development@qt-project.org
Subject: Re: [Development] High-DPI on Win
On Tuesday 29 December 2015 09:45:
2015, Mark De Wit escribió:
> Building from source would be an option, I guess. We have done it in
> the past, but the build process / flags (for distribution) is not
> sufficiently well documented, and starting with 5.5.1 we were excited
> to be able to use official binaries.
When
2015 13:31
To: Shaw Andy <andy.s...@theqtcompany.com>
Cc: Mark De Wit <mark.de...@iesve.com>; development@qt-project.org
Subject: Re: [Development] Please do not remove QtWebkit from 5.6 official
binaries
On Dec 3, 2015, at 8:31 AM, Shaw Andy
<andy.s...@theqtcompany.co
regards,
Mark
From: Turunen Tuukka [mailto:tuukka.turu...@theqtcompany.com]
Sent: 03 December 2015 12:30
To: Mark De Wit <mark.de...@iesve.com>; development@qt-project.org
Subject: RE: [Development] Please do not remove QtWebkit from 5.6 official
binaries
Hi Mark,
If you need to use Qt
34 matches
Mail list logo
