Scott Bloom wrote in
news:BYAPR10MB309616B1C72EF13816384DA6A9B69__18000.3636678279$1678065097$
gmane$o...@byapr10mb3096.namprd10.prod.outlook.com:
> --_000_BYAPR10MB309616B1C72EF13816384DA6A9B69BYAPR10MB3096namp_
> I have an external executable (mkvalidator from
>
Thiago Macieira wrote in
news:5359579.29KlJPOoH8__16072.5475566991$1675548885$gmane$org@tjmaciei-m
obl5:
>> They are binary-compatible. You can use MSVC 2022 with DLLs that were
>> built with MSVC 2019.
>
> Expanding a bit more: there's one build of Qt for both compilers.
> Though I guess this
Thiago Macieira wrote in
news:2741742.BEx9A2HvPv__44352.1315975644$1674404321$gmane$org@tjmaciei-m
obl5:
> So, are you still
> sticking to older MSVC releases years after there's a new one? Why?
Because when I run the maintnance tool for 6.4.2, I see MSVC 2019, but not
2022 (even after
Spam detection software, running on the system "mx.qt-project.org",
has identified this incoming email as possible spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
the administrator of that system for details.
=?UTF-8?Q?Andr=c3=a9_Hartmann?= wrote in
news:53425236-eff5-6309-2afb-087b32026...@iseg-hv.de:
> looks like QTBUG-65001 which should be fixed for 5.10.1.
Thanks. That bug report lists multiple monitors as a possible cause. I
have 2 monitors, and I just tried
I'm seeing restoreOverrideCursor() not working in Qt widget applications
built with Qt 5.10 under Windows 7. The normal cursor only returns when it
moves off the app, or at least off the widget it was over when the
hourglass was turned on. 32-bit MinGW and 64-bit MSVC2017 both do this. I
Kai Koehne wrote in
news:db6pr0201mb2135167cdab4996d782bf16d98...@db6pr0201mb2135.eurprd02.pr
od.outlook.com:
>> The reason for wanting everything to be signed is that Windows
>> Defender may flag unsigned executables as possible malware.
>
> If this does help with the false
Qt packages I download from www.qt.io are digitally signed by The Qt
Company, but Windows DLLs inside those packages are not signed. I have
purchased a code signing cert. Is it ok if I sign the Qt DLLs distributed
with my application? (The app is GPL and it uses otherwise unmodified Qt
Konstantin Podsvirov wrote in
news:780001467316...@web5o.yandex.ru:
> A don't have a folder C:\Qt\Docs\Qt-5.6\global with global qdoc
> configurations.
This directory seems to move around with different Qt versions. My install
path is non-standard, but I have the
Koehne Kai wrote in
news:db3pr02mb234cb67218a0ca98b8f9948e1...@db3pr02mb234.eurprd02.prod.out
look.com:
> Finally, if you target Windows versions older than Windows 7, you'll
> loose numeric string collation.
>
> In summary, most people won't notice :)
I nominally
10 matches
Mail list logo