On 9/7/2021 11:31 PM, Shawn Rutledge wrote:
On 2021 Sep 7, at 22:13, Alexander Dyagilev wrote:
For example, we do use MessageDialog component. In Qt5, it requires import
QtQuick.Dialogs 1.3, and in Qt6 - import Qt.labs.platform 1.1.
You can use Qt.labs.platform in both versions.
No, I can'
> On 2021 Sep 7, at 22:13, Alexander Dyagilev wrote:
>
> For example, we do use MessageDialog component. In Qt5, it requires import
> QtQuick.Dialogs 1.3, and in Qt6 - import Qt.labs.platform 1.1.
You can use Qt.labs.platform in both versions.
> Is it possible to import different modules depe
Hello,
We would like to migrate to Qt6. However, we still need to be able to
build our project with Qt5 to continue supporting Windows 7 OS (15% of
our users are still using it).
For now, I've managed to make C++ part support both Qt6 and Qt5.
However, it seems that QML part is not so easy.
On Tuesday, 7 September 2021 10:57:38 PDT Konstantin Tokarev wrote:
> If generated makefiles were non-recursive, it would be even faster.
Right. There are a couple of points during the build that the processor is
idle waiting for something to finish building before the next thing can start.
Ther
OK, thanks. I will not attempt to modify the registry. I just want to
know if that is the case and eventually display a warning.
The key for that is
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\FTH\State
Now I want to test my changes, I have already forced more than 100
crashes in the hope
07.09.2021, 20:53, "Thiago Macieira" :
> On Tuesday, 7 September 2021 02:52:49 PDT Tor Arne Vestbø wrote:
>> Good to hear!
>>
>> Part of it comes from CMake generating ninja files instead of Makefiles.
>
> Our qmake-generated Makefiles weren't that slow. Nothing compared to Automake,
> at least
On Tuesday, 7 September 2021 02:52:49 PDT Tor Arne Vestbø wrote:
> Good to hear!
>
> Part of it comes from CMake generating ninja files instead of Makefiles.
Our qmake-generated Makefiles weren't that slow. Nothing compared to Automake,
at least.
Qt 5 qtbase/src build:
Build succeeded, took 3:0
You shouldn’t need it for a read of the registry, however it is possible that
the IT dept of the user, or the user themselves has escalated the default
privileges required to read from HKLM
You might want to code your check to allow for a security violation, so the is
it enabled would be yes, n
Thank you very much that is the way. Do you know if elevated privileges
are needed to do that?
--Philippe
Le 07-09-2021 15:22, Jérôme Godbout a écrit :
You can put your aplicaiton into the exclude list, sorry though it was
mentionned into the microowft page, but here is the registry key:
HK
> On 7 Sep 2021, at 11:31, maitai wrote:
>
> Hi,
>
> I have some users (mainly beta testers) that are suffering from "Windows
> Tolerant Heap"
> (https://docs.microsoft.com/en-us/windows/win32/win7appqual/fault-tolerant-heap).
> The consequence of this being activated after some crashes is th
Good to hear!
Part of it comes from CMake generating ninja files instead of Makefiles.
Cheers,
Tor Arne
On 7 Sep 2021, at 11:26, Nuno Santos
mailto:nuno.san...@imaginando.pt>> wrote:
Hey,
Just want to share this random piece of feedback.
I have found a brutal difference between compiling Qt
Hi,
I have some users (mainly beta testers) that are suffering from "Windows
Tolerant Heap"
(https://docs.microsoft.com/en-us/windows/win32/win7appqual/fault-tolerant-heap).
The consequence of this being activated after some crashes is that the
application becomes very slow, plus some mysteri
Hey,
Just want to share this random piece of feedback.
I have found a brutal difference between compiling Qt 5 and Qt 6 from source.
Qt 6 compiles extremely fast.
Are this the benefits of using cmake to build it?
Big props to Qt team!
Best,
Nuno
_
13 matches
Mail list logo
