[Interest] Faster QXmlStreamWriter?

[Vadim Peretokin]

I'm looking at optimizing an applications save performance - it is too slow
right now and causes too much of a freeze. We're using QXmlStreamWriter,
here's the implementation
.

Profiling suggests that Qt's write element / attribute method is too slow (
screenshot , results attached). Is there
anything I can do it speed it up? I tried giving it a QBuffer instead of a
QFile, but the difference was marginal.

A lot of time seems to be spent resizing the buffer, and unfortunately
there doesn't seem to be a way to pre-set the QBuffer size to something
reasonable to begin with.

Anyone have tips?
"Function / Call Stack","CPU Time","Module","Function (Full)","Source File","Start Address"
"QIODevice::write","0.0399935","libQt5Core.so.5","QIODevice::write(char const*, long long)","[Unknown]","0x1ad360"
" func@0x310fe0","0.0399935","libQt5Core.so.5","func@0x310fe0","[Unknown]","0x310fe0"
"  func@0x3111b0 <- func@0x312d60 <- QXmlStreamWriter::writeStartElement <- QXmlStreamWriter::writeTextElement <- XMLexport::writeTrigger <- XMLexport::writeTrigger <- XMLexport::writeTrigger <- XMLexport::writeTrigger <- XMLexport::writeHost <- XMLexport::exportHost <- Host::saveProfile <- TLuaInterpreter::saveProfile <- lua_pcall <- TLuaInterpreter::call <- TAlias::execute <- TAlias::match <- AliasUnit::processDataStream <- Host::send <- TCommandLine::enterCommand <- TCommandLine::event <- QApplicationPrivate::notify_helper <- QApplication::notify <- QCoreApplication::notifyInternal2 <- func@0x1b22b0 <- QApplicationPrivate::notify_helper <- QApplication::notify <- QCoreApplication::notifyInternal2 <- QGuiApplicationPrivate::processKeyEvent <- QGuiApplicationPrivate::processWindowSystemEvent <- QWindowSystemInterface::sendWindowSystemEvents <- func@0xd8b70 <- QEventLoop::exec <- QCoreApplication::exec <- main <- __libc_start_main <- _start","0.0199958","libQt5Core.so.5","func@0x3111b0","[Unknown]","0x3111b0"
"  QXmlStreamWriter::writeAttribute <- XMLexport::writeAction <- XMLexport::writeAction <- XMLexport::writeAction <- XMLexport::writeHost <- XMLexport::exportHost <- Host::saveProfile <- TLuaInterpreter::saveProfile <- lua_pcall <- TLuaInterpreter::call <- TAlias::execute <- TAlias::match <- AliasUnit::processDataStream <- Host::send <- TCommandLine::enterCommand <- TCommandLine::event <- QApplicationPrivate::notify_helper <- QApplication::notify <- QCoreApplication::notifyInternal2 <- func@0x1b22b0 <- QApplicationPrivate::notify_helper <- QApplication::notify <- QCoreApplication::notifyInternal2 <- QGuiApplicationPrivate::processKeyEvent <- QGuiApplicationPrivate::processWindowSystemEvent <- QWindowSystemInterface::sendWindowSystemEvents <- func@0xd8b70 <- QEventLoop::exec <- QCoreApplication::exec <- main <- __libc_start_main <- _start","0.011999","libQt5Core.so.5","QXmlStreamWriter::writeAttribute(QString const&, QString const&)","[Unknown]","0x3115e0"
"  func@0x312d60 <- QXmlStreamWriter::writeStartElement <- QXmlStreamWriter::writeTextElement <- XMLexport::writeTrigger <- XMLexport::writeTrigger <- XMLexport::writeTrigger <- XMLexport::writeHost <- XMLexport::exportHost <- Host::saveProfile <- TLuaInterpreter::saveProfile <- lua_pcall <- TLuaInterpreter::call <- TAlias::execute <- TAlias::match <- AliasUnit::processDataStream <- Host::send <- TCommandLine::enterCommand <- TCommandLine::event <- QApplicationPrivate::notify_helper <- QApplication::notify <- QCoreApplication::notifyInternal2 <- func@0x1b22b0 <- QApplicationPrivate::notify_helper <- QApplication::notify <- QCoreApplication::notifyInternal2 <- QGuiApplicationPrivate::processKeyEvent <- QGuiApplicationPrivate::processWindowSystemEvent <- QWindowSystemInterface::sendWindowSystemEvents <- func@0xd8b70 <- QEventLoop::exec <- QCoreApplication::exec <- main <- __libc_start_main <- _start","0.0079987","libQt5Core.so.5","func@0x312d60","[Unknown]","0x312d60"
"QBuffer::writeData","0.036005","libQt5Core.so.5","QBuffer::writeData(char const*, long long)","[Unknown]","0x18f650"
"QByteArray::resize","0.0279967","libQt5Core.so.5","QByteArray::resize(int)","[Unknown]","0xb02e0"
"__GI_","0.0200273","libc.so.6","long double __GI_(long, int, bool, char)","malloc.c","0x8fa00"
"__GI_","0.0160065","libc.so.6","float __GI_(long, int, bool, char)","malloc.c","0x8f3e0"
"__GI___libc_malloc","0.0120044","libc.so.6","__GI___libc_malloc","malloc.c","0x8eeb0"
"QByteArray::QByteArray","0.0120013","libQt5Core.so.5","QByteArray::QByteArray(int, Qt::Initialization)","[Unknown]","0xb0050"
"qCalculateGrowingBlockSize","0.0119998","libQt5Core.so.5","qCalculateGrowingBlockSize(unsigned long, unsigned long, unsigned long)","[Unknown]","0xaf6b0"
"operator==","0.0119998","libQt5Core.so.5","operator==(QString const&, QStringRef const&)","[Unknown]","0x12cbf0"
"xcb_wait_for_event","0.01","libxcb.so.1","xcb_wait_for_event","[Unknown]","0xd4f0"
"__memcpy_sse2_unaligned_erms","0.01","libc.so.6","__memcpy_sse

Re: [Interest] Faster QXmlStreamWriter?

[Vadim Peretokin]

Thanks! That helped remove the resize operation from the profiling data,
but QBuffer::writeData is still there, and the overall time didn't change
much.

Is there anything else I can look at, or is this a dead end then - requires
a different serialization solution altogether (a lot of work)?

On Sun, Apr 22, 2018 at 4:53 PM Giuseppe D'Angelo 
wrote:

> Il 22/04/2018 16:30, Vadim Peretokin ha scritto:
> > A lot of time seems to be spent resizing the buffer, and unfortunately
> > there doesn't seem to be a way to pre-set the QBuffer size to something
> > reasonable to begin with.
> >
> > Anyone have tips?
>
> Didn't check the actual code, but you can always resize a QBuffer
> internal bytearray:
>
> QBuffer b;
> b.buffer().resize(1234); // or reserve()
>
> HTH,
>
> --
> Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
> KDAB (France) S.A.S., a KDAB Group company
> Tel. France +33 (0)4 90 84 08 53 <+33%204%2090%2084%2008%2053>,
> http://www.kdab.com
> KDAB - The Qt, C++ and OpenGL Experts
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
"Function","CPU Time: Total","CPU Time: Self","Module","Function (Full)","Source File","Start Address"
"QEventLoop::exec","0.27","0","libQt5Core.so.5","QEventLoop::exec(QFlags)","[Unknown]","0x27d7b0"
"main","0.26","0","mudlet","main","main.cpp","0x6cdf0"
"func@0xd8b70","0.26","0","libQt5XcbQpa.so.5","func@0xd8b70","[Unknown]","0xd8b70"
"__libc_start_main","0.26","0","libc.so.6","__libc_start_main","libc-start.c","0x210d0"
"_start","0.26","0","mudlet","_start","[Unknown]","0x72500"
"QCoreApplication::exec","0.26","0","libQt5Core.so.5","QCoreApplication::exec(void)","[Unknown]","0x2863a0"
"QCoreApplication::notifyInternal2","0.25","0","libQt5Core.so.5","QCoreApplication::notifyInternal2(QObject*, QEvent*)","[Unknown]","0x27ef20"
"QApplication::notify","0.25","0","libQt5Widgets.so.5","QApplication::notify(QObject*, QEvent*)","[Unknown]","0x160760"
"QApplicationPrivate::notify_helper","0.25","0","libQt5Widgets.so.5","QApplicationPrivate::notify_helper(QObject*, QEvent*)","[Unknown]","0x1595a0"
"func@0x1b22b0","0.21","0","libQt5Widgets.so.5","func@0x1b22b0","[Unknown]","0x1b22b0"
"TCommandLine::event","0.21","0","mudlet","TCommandLine::event(QEvent*)","TCommandLine.cpp","0x3164a0"
"TCommandLine::enterCommand","0.21","0","mudlet","TCommandLine::enterCommand(QKeyEvent*)","TCommandLine.cpp","0x315ad0"
"lua_pcall","0.21","0","liblua5.1.so.0","lua_pcall","[Unknown]","0x83a0"
"Host::send","0.21","0","mudlet","Host::send(QString, bool, bool)","Host.cpp","0x27de20"
"AliasUnit::processDataStream","0.21","0","mudlet","AliasUnit::processDataStream(QString const&)","AliasUnit.cpp","0x18dd10"
"QGuiApplicationPrivate::processKeyEvent","0.21","0","libQt5Gui.so.5","QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*)","[Unknown]","0x12ef30"
"QGuiApplicationPrivate::processWindowSystemEvent","0.21","0","libQt5Gui.so.5","QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)","[Unknown]","0x133fd0"
"QWindowSystemInterface::sendWindowSystemEvents","0.21","0","libQt5Gui.so.5","QWindowSystemInterface::sendWindowSystemEvents(QFlags)","[Unknown]","0x10f770"
"TAlias::match","0.21","0","mudlet","TAlias::match(QString const&)","TAlias.cpp","0x2ee310"
"TAlias::execute","0.21&q

Re: [Interest] Faster QXmlStreamWriter?

[Vadim Peretokin]

On Mon, Apr 23, 2018 at 8:32 AM Thiago Macieira 
wrote:

> On Sunday, 22 April 2018 22:15:48 PDT Vadim Peretokin wrote:
> > Thanks! That helped remove the resize operation from the profiling data,
> > but QBuffer::writeData is still there, and the overall time didn't change
> > much.
> >
> > Is there anything else I can look at, or is this a dead end then -
> requires
> > a different serialization solution altogether (a lot of work)?
>
> Correct, QBuffer is not optimised for speed. I ran into that while
> developing
> QCborStreamWriter. The solution was to bypass it for speed.
>
>
OK, that's a pity. I'll look into using pugixml instead, and if anyone else
knows a faster XML serializer, I'd he happy to hear about it.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Faster QXmlStreamWriter?

[Vadim Peretokin]

On Tue, Apr 24, 2018 at 8:14 AM Thiago Macieira 
wrote:

> On Monday, 23 April 2018 22:02:20 PDT Vadim Peretokin wrote:
> > > Correct, QBuffer is not optimised for speed. I ran into that while
> > > developing
> > > QCborStreamWriter. The solution was to bypass it for speed.
> >
> > OK, that's a pity. I'll look into using pugixml instead, and if anyone
> else
> > knows a faster XML serializer, I'd he happy to hear about it.
>
> Any chance you can choose a different serialisation format?
>
>
We're thinking on the consequences of that - if pugixml isn't fast enough
still, will look at a different format. Recommendations welcome! :)
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QFile::write(const QByteArray&) does not write all data?

[Vadim Peretokin]

Obvious question but do you flush?

On Wed, May 9, 2018 at 11:09 AM alexander golks  wrote:

> hi,
>
> i recently stumbled over this situation, running on windows 7 using
> qt-5.6.3.
> when trying to write ~50MB of data, write does not always complete, the
> file does not contain all data,
> yet no error is returned.
>
> i always thought, QFile::write(const QByteArray&) is meant to write all
> data.
> as stated in the documentation for: qint64 QIODevice::writeData(const char
> *data, qint64 maxSize)
> "When reimplementing this function it is important that this function
> writes all the data available before returning."
>
> is this a bug in QFile?
> or do i have to do-while loop to write the rest of my data?
> but wouldn't this lead missing writes in QDataStream + QFile, as
> QDataStream needs complete writes, too?
>
> alex
>
> --
> /*
>  *  Learn to pause -- or nothing worthwhile can catch up to you.
>  */
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Faster QXmlStreamWriter?

[Vadim Peretokin]

I went with pugixml (https://pugixml.org) for anyone interested and the
speed savings are worth it. It is also fairly easy to transition from qml
to pugixml and as a bonus, it does not choke on non-printable characters.

On Sun, Apr 29, 2018 at 10:58 PM Gunnar Roth  wrote:

> >Hi Thiago
>
> >
> >PS: YMMV, especially if you don't use CPU-optimised UTF-8 methods like
> >I do.
> >You need to compile your own Qt to get those.
> >
> Could you please give more information about this? I thought sse2 code
> for utf8 is enabled by default at least in 64 bit build. What do I miss
> here?
>
> Regards,
> Gunnar Roth
>
>
> >
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt internalisation support for C++11 raw literals

[Vadim Peretokin]

On Sun, Oct 8, 2017 at 1:05 PM Vadim Peretokin  wrote:

> Is anyone running a C++ project that does their translation with Qt? I'm
> having trouble with lupdate barfing on raw literals and found a
> corresponding bug report <https://bugreports.qt.io/browse/QTBUG-42736> on
> it.
>
> I find it hard to believe that the "most widely used C++ framework"
> doesn't support raw literals in i18n 6 years after the standard was
> released, so I hope I'm in the wrong on this.
>

Anyone else dealing with this or have workarounds? I'd like to be able to
use a 7 year old C++ feature in my code :(
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Compiling Qt for Webassembly

[Vadim Peretokin]

I'm trying to compile Qt 5.12.0 for webassembly, but it has compile errors:
https://hastebin.com/vovisayapi.bash

This is on Ubuntu 18.04, emcc 1.38.12 (commit
0d8576c0e8f5ee09a36120b9d44184b5da2f2e7a), gcc 7.3.0. Any ideas what's
going wrong?

(I wouldn't mind trying the latest Qt sources, except that "Getting the code
" instructions are
ambigious: what am I supposed to with 3 different directories?)

Thanks!
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Compiling Qt for Webassembly

[Vadim Peretokin]

Thanks, that worked!

It says uitools, multimedia, and concurrent isn't available. The latter two
I understand, but is uitools supposed not to be available?

On Sat, Oct 6, 2018 at 10:02 AM Lorn Potter  wrote:

> Hello Vadim,
>
>
> On 06/10/18 15:08, Vadim Peretokin wrote:
> > I'm trying to compile Qt 5.12.0 for webassembly, but it has compile
> > errors: https://hastebin.com/vovisayapi.bash
> >
> > This is on Ubuntu 18.04, emcc 1.38.12 (commit
> > 0d8576c0e8f5ee09a36120b9d44184b5da2f2e7a), gcc 7.3.0. Any ideas what's
> > going wrong?
>
>
> For the 5.12-beta1 package, you need this patch:
> https://codereview.qt-project.org/#/c/241987/ to get through the wasm
> build for qtnetworkauth
>
> (also attached)
>
>
> >
> > (I wouldn't mind trying the latest Qt sources, except that "Getting the
> > code <https://wiki.qt.io/Qt_for_WebAssembly#Getting_the_code>"
> > instructions are ambigious: what am I supposed to with 3 different
> > directories?)
>
> For just Qt, you only need qtbase, really. If you want to develop with
> QtQuick/Qml, you will need qtdeclarative as well.
>
> git clone -b 5.12 https://code.qt.io/qt/qtbase.git
>
> There are only a few modules we have tested for wasm - qmqtt, qtwebsockets.
>
> There is a pending patch for qtsensors support (basically just accel,
> but others for firefox)
> https://codereview.qt-project.org/#/c/217457/
>
> -
> Lorn
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt Install Framework - Becoming a Microsoft Known Publisher

[Vadim Peretokin]

Here's how we do code signing in CI with Mudlet for our Qt project:
https://github.com/Mudlet/Mudlet/blob/development/CI/appveyor.after_success.ps1

Note that we use Squirrel, not the Qt Install Framework - Squirrel is much
more user-friendly.

- Vadim.

On Tue, Oct 9, 2018 at 6:04 PM Nuno Santos  wrote:

> Nils,
>
> This is good stuff! Thanks for sharing.
>
> This will definitely help with the CI process.
>
> Best,
>
> Nuno
>
> > On 9 Oct 2018, at 16:58, Nils Jeisecke 
> wrote:
> >
> > Am 09.10.2018 um 16:29 hat Nuno Santos geschrieben:
> >> There are several providers for this. Globalsign is just one. Then you
> will receive a usb dongle with your certificate (GlobalSign sends a USB
> dongle).
> > Yeah, and the glorious signtool will ask for a PIN every time your
> > automated build signs the executable...
> >
> > Not Qt related at all but just in case someone is interested - This is
> > an alternative signing client implementation that allows the PIN to be
> > specified on the command line (there are probably more secure ways, but
> > you need that super secure USB token anyway...):
> >
> > https://pastebin.com/6iYNKLpN
> >
> > See the stackoverflow link for pointers on how to export the
> > certificate.
> >
> > Nils
> >
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt Install Framework - Becoming a Microsoft Known Publisher

[Vadim Peretokin]

No, we pay a separate fee for Apple signing.

On Tue, Oct 9, 2018 at 6:45 PM Andy  wrote:

> While we're on the subject...
>
> I've been trying to find out if one can use the Apple dev cert to sign
> Windows desktop apps as well - does anyone know if this is possible? Two
> birds/one stone?
>
> Thanks!
>
> ---
> Andy Maloney  //  https://asmaloney.com
> twitter ~ @asmaloney <https://twitter.com/asmaloney>
>
>
>
> On Tue, Oct 9, 2018 at 12:17 PM Vadim Peretokin 
> wrote:
>
>> Here's how we do code signing in CI with Mudlet for our Qt project:
>> https://github.com/Mudlet/Mudlet/blob/development/CI/appveyor.after_success.ps1
>>
>> Note that we use Squirrel, not the Qt Install Framework - Squirrel is
>> much more user-friendly.
>>
>> - Vadim.
>>
>> On Tue, Oct 9, 2018 at 6:04 PM Nuno Santos 
>> wrote:
>>
>>> Nils,
>>>
>>> This is good stuff! Thanks for sharing.
>>>
>>> This will definitely help with the CI process.
>>>
>>> Best,
>>>
>>> Nuno
>>>
>>> > On 9 Oct 2018, at 16:58, Nils Jeisecke 
>>> wrote:
>>> >
>>> > Am 09.10.2018 um 16:29 hat Nuno Santos geschrieben:
>>> >> There are several providers for this. Globalsign is just one. Then
>>> you will receive a usb dongle with your certificate (GlobalSign sends a USB
>>> dongle).
>>> > Yeah, and the glorious signtool will ask for a PIN every time your
>>> > automated build signs the executable...
>>> >
>>> > Not Qt related at all but just in case someone is interested - This is
>>> > an alternative signing client implementation that allows the PIN to be
>>> > specified on the command line (there are probably more secure ways, but
>>> > you need that super secure USB token anyway...):
>>> >
>>> > https://pastebin.com/6iYNKLpN
>>> >
>>> > See the stackoverflow link for pointers on how to export the
>>> > certificate.
>>> >
>>> > Nils
>>> >
>>>
>>> ___
>>> Interest mailing list
>>> Interest@qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/interest
>>>
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
>>
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt Install Framework - Becoming a Microsoft Known Publisher

[Vadim Peretokin]

The only path is to pay. Had the same problem, we got users to donate.

On Wed, 10 Oct. 2018, 9:00 am Michael Corcoran, <
michael.corco...@outlook.com> wrote:

> I've looked into this a few times but never really came to a satisfying
> conclusion. Does anybody know a viable path for free and open source
> projects? The warnings scare some users off, but I'm sure I'm not alone
> when I say not about to pay out of my own pocket to better support a
> platform I don't even use myself, and worse still, one that seems to be
> actively hostile toward my efforts to support it.
>
> Thanks,
> Michael
> --
> *From:* Interest  outlook@qt-project.org> on behalf of Elvis Stansvik <
> elvst...@gmail.com>
> *Sent:* Wednesday, 10 October 2018 6:54 AM
> *To:* Nuno Santos
> *Cc:* interest@qt-project.org Interest
>
> *Subject:* Re: [Interest] Qt Install Framework - Becoming a Microsoft
> Known Publisher
>
> Den tis 9 okt. 2018 kl 17:54 skrev Elvis Stansvik :
> >
> > Den tis 9 okt. 2018 17:29Nuno Santos  skrev:
> >>
> >> Christopher,
> >>
> >> In order to have Microsoft’s SmartScreen saying your company name, you
> need to buy a EV certificate:
> >
> >
> > Let me add that it's not strictly necessary to use an EV certificate to
> get rid of SmartScreen. It's possible with a "regular" certificate as well,
> it just takes some time for the cert signature to become whitelisted at
> Microsoft (they track user installs).
> >
> > We use a regular (cheaper) code signing cert from Digicert. For a while,
> users running our installer would still get a SmartScreen warning, but as
> the number of installs grew, at some point the warning disappeared due to
> whitelisting.
>
> For reference, our 3 year Digicert Code Signing Certificate was 535
> USD when we bought it.
>
> For signing the macOS application/dmg we use a separate certificate
> from Apple we get through their developer program (999 SEK ~ 110 USD).
> It's possible that we could use the Digicert one to sign the macOS
> build, or vice versa use the Apple one to sign the Windows build, but
> I doubt it and haven't investigated, since it's not so much money
> anyway.
>
> Elvis
>
> >
> > An EV certificate would establish trust faster, and I think the rules
> behind the whitelisting is rather undocumented.
> >
> > HTH,
> > Elvis
> >
> >>
> >>
> https://www.globalsign.com/en/code-signing-certificate/ev-code-signing-certificates/
> >>
> >> It costs around 300 euros a year.
> >>
> >> There are several providers for this. Globalsign is just one. Then you
> will receive a usb dongle with your certificate (GlobalSign sends a USB
> dongle).
> >>
> >> When you have it, you need to configure it. The provider tells you what
> to do.
> >>
> >> After that you need to invoke a command like this:
> >>
> >>
> >> signtool.exe sign /a /tr
> http://rfc3161timestamp.globalsign.com/advanced /td SHA256 EXE_TO_SIGN
> >>
> >>
> >> Best,
> >>
> >> Nuno
> >>
> >> On 9 Oct 2018, at 16:20, Christopher Probst 
> wrote:
> >>
> >> Thank-you Nils for your reply.
> >>
> >>> I think signing your installer should solve this. "Trust" can be bought
> >>> with the certificate.
> >>>
> >>>
> >>
> >>
> >> Please forgive my ignorance, but how does one sign an application with
> Microsoft? The documentation online seems unnecessary complex for something
> that should be routine. Any help is appreciated.
> >>
> >> Thanks,
> >> Christopher
> >> ___
> >> Interest mailing list
> >> Interest@qt-project.org
> >> http://lists.qt-project.org/mailman/listinfo/interest
> >>
> >>
> >> ___
> >> Interest mailing list
> >> Interest@qt-project.org
> >> http://lists.qt-project.org/mailman/listinfo/interest
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Compiling Qt for Webassembly

[Vadim Peretokin]

Would anyone know why uitools isn't available?

On Sat, Oct 6, 2018 at 12:42 PM Vadim Peretokin 
wrote:

> Thanks, that worked!
>
> It says uitools, multimedia, and concurrent isn't available. The latter
> two I understand, but is uitools supposed not to be available?
>
> On Sat, Oct 6, 2018 at 10:02 AM Lorn Potter  wrote:
>
>> Hello Vadim,
>>
>>
>> On 06/10/18 15:08, Vadim Peretokin wrote:
>> > I'm trying to compile Qt 5.12.0 for webassembly, but it has compile
>> > errors: https://hastebin.com/vovisayapi.bash
>> >
>> > This is on Ubuntu 18.04, emcc 1.38.12 (commit
>> > 0d8576c0e8f5ee09a36120b9d44184b5da2f2e7a), gcc 7.3.0. Any ideas what's
>> > going wrong?
>>
>>
>> For the 5.12-beta1 package, you need this patch:
>> https://codereview.qt-project.org/#/c/241987/ to get through the wasm
>> build for qtnetworkauth
>>
>> (also attached)
>>
>>
>> >
>> > (I wouldn't mind trying the latest Qt sources, except that "Getting the
>> > code <https://wiki.qt.io/Qt_for_WebAssembly#Getting_the_code>"
>> > instructions are ambigious: what am I supposed to with 3 different
>> > directories?)
>>
>> For just Qt, you only need qtbase, really. If you want to develop with
>> QtQuick/Qml, you will need qtdeclarative as well.
>>
>> git clone -b 5.12 https://code.qt.io/qt/qtbase.git
>>
>> There are only a few modules we have tested for wasm - qmqtt,
>> qtwebsockets.
>>
>> There is a pending patch for qtsensors support (basically just accel,
>> but others for firefox)
>> https://codereview.qt-project.org/#/c/217457/
>>
>> -
>> Lorn
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
>>
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] tr() a string while ignoring context?

[Vadim Peretokin]

I'd like to translate a string while ignoring the context of it, but
QCoreApplication::translate("", sourceText.toUtf8().constData()) isn't
cutting it. Any ideas on what would work?
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] tr() a string while ignoring context?

[Vadim Peretokin]

I tried QObject::tr but I'm still having difficulty. I'd like to translate
dynamic input that's not known as compile-time.

Basically, I'd like to expose the wealth of translations already available
for my application to my scripting layer, and as you can see that means the
context needs to be stripped out - so given any input string, return the
first known translation, irregardless of the context. Is this feasible and
am I just misunderstanding you?

- Vadim

On Fri, Nov 9, 2018 at 5:52 PM Andy  wrote:

> Aside from QObject::tr() which works without a context string, I think
> QT_TR_NOOP() is the only other one without a context.
>
>
> https://doc.qt.io/qt-5/i18n-source-translation.html#using-qt-tr-noop-and-qt-translate-noop-in-c
>
> Note that QObject::tr can be used outside the class. See
> some_global_function example here:
>
>
> https://doc.qt.io/qt-5/i18n-source-translation.html#using-qcoreapplication-translate
>
> Also of interest might be "Translating Non-Qt Classes":
>
>
> https://doc.qt.io/qt-5/i18n-source-translation.html#translating-non-qt-classes
>
> ---
> Andy Maloney  //  https://asmaloney.com
> twitter ~ @asmaloney <https://twitter.com/asmaloney>
>
>
>
> On Fri, Nov 9, 2018 at 11:12 AM Vadim Peretokin 
> wrote:
>
>> I'd like to translate a string while ignoring the context of it, but
>> QCoreApplication::translate("", sourceText.toUtf8().constData()) isn't
>> cutting it. Any ideas on what would work?
>>
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
>>
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Interest Digest, Vol 86, Issue 17

[Vadim Peretokin]

Since switching to AppImage, our Qt application stopped having the majority
of Linux distribution-specific deployment images and it's been mostly
trouble-free. I can recommend it. It also does not require any kind of an
internet connection.

On Sat, Nov 17, 2018 at 3:19 PM Roland Hughes 
wrote:

> Alexander:
>
> Having burned multiple days with
> https://github.com/probonopd/linuxdeployqt
>
> I need to warn you, it is only for simple applications which can compile
> on Ubuntu 14.04 using a dated version of Qt. If you need a current
> webengine or other current features you will be resoundingly disappointed.
> If your application has plug-ins (be they browser or some other kind) the
> tool isn't good at finding their library dependencies. They also refuse to
> add a -include-lib-dir type switch were you could park all of the libraries
> it missed so it could easily scoop them up.
>
> This may or may not be an issue for you, but, AppImage is something of an
> inverted philosophy. It's not "one Deb to rule them all" which is how
> things were done in the past. Each AppImage is built specifically for the
> target. For us that was a complete show stopper. More than 90% of the
> machines running the application globally have zero Internet connection.
> One box, somewhere, does. It pulls down the package and installs on all of
> the other machines via sneaker-net. Hardware and OS version vary wildly.
> (At its Internet connection peak, 1 in 7 machines had Internet access. That
> has since been reduced.)
>
> Don't know if you will be providing support or not, but, from a support
> standpoint, you really have no idea what got delivered.
>
> What really floors me about the Linux world and even the Qt world with
> respect to Webengine or plug-ins, is this desperate clinging to dynamic
> linking. It was a bad idea which got worse over time. Take a look at the
> current AppImage path. Rather than admit dynamic linking was a failed
> experiment, they are now packaging entire dynamic libraries repeatedly.
>
> Back in the days of DOS, we only linked the functions we needed. Not the
> entire 300+Meg library we didn't need. Only a tiny set of INT-21 and 3
> other INTs were expected to be provided by the OS.
>
> While some will find it useful, Snappy hasn't delivered on its promises. I
> haven't spent enough time with Flatpak to say if it is taking the correct
> approach or is simply more the same.
>
> Just my 0.0002 cents. Having recently walked this road.
>
>
> On 11/16/18 10:52 AM, Alexander Dyagilev wrote:
> > Hello,
> >
> > On Windows we have windeployqt.
> >
> > On MAC - macdeployqt.
> >
> > On Linux - there is no tool for this ? Is there some convenient
> > alternative way to copy all the required Qt files then (my project uses
> > Quick Controls 2)?
>
> --
> Roland Hughes, President
> Logikal Solutions
> (630) 205-1593
>
> http://www.theminimumyouneedtoknow.com
> http://www.infiniteexposure.net
> http://www.johnsmith-book.com
> http://www.logikalblog.com
> http://www.interestingauthors.com/blog
> http://lesedi.us
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] How to get macdeployqt to ship QtSpeech plugin?

[Vadim Peretokin]

Hi!

How can I get Qt 5.12 macdeployqt to include QtSpeech plugin in the
distribution? My project makes use of it, QtSpeech plugin is available in
the Qt installation, but yet it is not getting added to the application.

Thanks,
Vadim.
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] How to get macdeployqt to ship QtSpeech plugin?

[Vadim Peretokin]

Aha! Thanks.

On Tue, Feb 12, 2019 at 9:48 PM Samuel Gaist  wrote:

> On 12 Feb 2019, at 18:05, Vadim Peretokin  wrote:
> >
> > Hi!
> >
> > How can I get Qt 5.12 macdeployqt to include QtSpeech plugin in the
> distribution? My project makes use of it, QtSpeech plugin is available in
> the Qt installation, but yet it is not getting added to the application.
> >
> > Thanks,
> > Vadim.
> > ___
> > Interest mailing list
> > Interest@qt-project.org
> > https://lists.qt-project.org/listinfo/interest
>
> Hi,
>
> You have to apply this patch:
>
> https://codereview.qt-project.org/#/c/253094/
>
> and build macdeployqt (nothing else is needed)
>
> Best regards
>
> Samuel
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] How to detect a HiDPI display with Qt?

[Vadim Peretokin]

I'm not clear on how to detect if a display is HiDPI with Qt. I've tried
QApplication.desktop()->screen()->devicePixelRatio() but even that returns
1 for a display that is 3840x2160.

Has anyone got hints on how to do this successfully?
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] Natural height of Qt QuickTexField

[Vadim Peretokin]

How can I get the 'natural' height of a Qt Quick Control 5.12 TextField?
For example if I want to change the height to X and then change it back to
the natural height, how can I do that?
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Natural height of Qt QuickTexField

[Vadim Peretokin]

Found it stumbling through some Qt code - setting it to 'undefined' does
the trick.

On Sat, May 18, 2019 at 2:32 PM Vadim Peretokin 
wrote:

> How can I get the 'natural' height of a Qt Quick Control 5.12 TextField?
> For example if I want to change the height to X and then change it back to
> the natural height, how can I do that?
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Linking issues with Angle and Qt 5.12.x

[Vadim Peretokin]

Are you mixing 64bit and 32bit libraries by accident during linking? I had
similar messages in that scenario.

On Mon, May 27, 2019 at 12:57 PM Oliver Wolff  wrote:

> Hi Frederico,
>
> I am not aware of an issue with ANGLE when using MinGW. Can you create a
> bug report on http://bugreports.qt.io/ ,attach a minimal example, and
> assign it to me so that it does not get lost?
>
> Olli
>
> On 25/05/2019 17:47, Federico Buti wrote:
> > Hi all.
> >
> > We are facing a quite strange behaviour with qnanopainter
> > .
> > Building/running the library and the examples works smoothly on Qt 5.9.8
> > and no issue is found. I guess everything was fixed there, see for
> > instance here
> > .
> >
> > Building the code on 5.12.x results in a similar linker issue as
> > depicted in the last link. In particular we have a series of undefined
> > references as shown below:
> >
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x12b):
>
> > undefined reference to `_imp__glDeleteTextures@8'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x1b4):
>
> > undefined reference to `glDeleteShader@4'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x1d5):
>
> > undefined reference to `glDeleteBuffers@8'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x1e5):
>
> > undefined reference to `glDeleteShader@4'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x1f5):
>
> > undefined reference to `glDeleteProgram@4'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x988):
>
> > undefined reference to `_imp__glBindTexture@8'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x9a0):
>
> > undefined reference to `_imp__glPixelStorei@8'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x9fc):
>
> > undefined reference to `_imp__glTexSubImage2D@36'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0xa43):
>
> > undefined reference to `_imp__glBindTexture@8'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x1361):
>
> > undefined reference to `_imp__glDeleteTextures@8'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x1388):
>
> > undefined reference to `_imp__glGetError@0'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x1407):
>
> > undefined reference to `_imp__glGenTextures@8'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x143a):
>
> > undefined reference to `_imp__glBindTexture@8'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x1442):
>
> > undefined reference to `_imp__glPixelStorei@8'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x14ae):
>
> > undefined reference to `_imp__glTexImage2D@36'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x14d7):
>
> > undefined reference to `_imp__glTexParameteri@12'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x1638):
>
> > undefined reference to `_imp__glBindTexture@8'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x16b9):
>
> > undefined reference to `glGenerateMipmap@4'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x16fa):
>
> > undefined reference to `_imp__glTexImage2D@36'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x171a):
>
> > undefined reference to `_imp__glTexParameteri@12'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x17e0):
>
> > undefined reference to `glUniform4fv@12'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x1828):
>
> > undefined reference to `_imp__glBindTexture@8'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x185f):
>
> > undefined reference to `_imp__glBindTexture@8'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x18bb):
>
> > undefined reference to `glGetProgramInfoLog@16'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x192e):
>
> > undefined reference to `glGetShaderInfoLog@16'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x19c9):
>
> > undefined reference to `glCreateProgram@0'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x19d7):
>
> > undefined reference to `glCreateShader@4'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x19e8):
>
> > undefined reference to `glCreateShader@4'
> >
> libqnanopainter.a(qnanobackendgles2.cpp.o):qnanobackendgles2.cpp:(.text+0x1a19):
>
> > undefined reference to `glShaderSour

[Interest] How to get QML ScrollView to scroll when children are reparented into it?

[Vadim Peretokin]

I'm reparenting a TextArea into a ScrollView - somewhat unsuccessfully,
because the said ScrollView then refuses to scroll.

What is the right way to go about it? I've stripped the problem down to a
small, reproducible usecase here:
https://transfer.sh/rYfth/dodgy-scrollview.zip

And here is the qml file inside that zip in full. I was told that 'parent:
addResourceScrollView' is the issue, but changing that just lead to a host
of issues that lead down a rabbit hole.

import QtQuick 2.7import QtQuick.Controls 2.5import
QtQuick.Controls.Material 2.0import QtQuick.Window 2.10import
QtQuick.Controls.Universal 2.12import QtQuick.Layouts 1.12import
QtQuick.Dialogs 1.3

ApplicationWindow {
id: window
visible: true
width: 640; height: 480
minimumWidth: 550; minimumHeight: 300
title: qsTr("Hammer")

Page {
id: addResourcesPage
width: window.width
height: window.height - buttonsRow.height


ScrollView {
id: addResourceScrollView
height: parent.height; width: parent.width;
visible: textArea.state === "EXPANDED"
clip: true

onContentHeightChanged: console.log(`content height changed`)
onContentChildrenChanged: console.log(`children changed;
now have: ${children.length}`)
onChildrenRectChanged: console.log(`children rect changed`)
}

Label {
id: hammerLabel
anchors.horizontalCenter: parent.horizontalCenter
y: 120
text: qsTr("🔨 Hammer")
font.bold: true
opacity: 0.6
font.pointSize: 36
font.family: "Apple Color Emoji"
visible: textArea.state === "MINIMAL"
}

Row {
id: loadResourcesRow
y: hammerLabel.y + 80
anchors.horizontalCenter: parent.horizontalCenter
spacing: 10

Button {
id: loadResourceButton
text: qsTr("Button")
visible: textArea.state === "MINIMAL"
}

TextArea {
id: textArea
placeholderText: qsTr("or load it here")
renderType: Text.NativeRendering
// ensure the tooltip isn't monospace, only the text
font.family: text ? "Ubuntu Mono" : "Ubuntu"
selectByMouse: true
wrapMode: "WrapAtWordBoundaryOrAnywhere"

// ensure focus remains when the area is reparented
onWidthChanged: textArea.forceActiveFocus()
// it doesn't have focus on startup
Component.onCompleted: textArea.focus = false

states: [
State {
name: "MINIMAL"; when: !textArea.text
ParentChange {
target: textArea
parent: loadResourcesRow
width: 300
height: undefined
}
},
State {
name: "EXPANDED"; when: textArea.text
ParentChange {
target: textArea
parent: addResourceScrollView
x: 0; y: 0
width: window.width
height: window.height
}
}
]
state: "MINIMAL"

transitions: Transition {
ParentAnimation {
NumberAnimation { properties:
"x,y,width,height";  easing.type: Easing.InCubic; duration: 600 }
}
}
}

}

Text {
id: experimentalText
anchors.horizontalCenter: parent.horizontalCenter
anchors.verticalCenter: parent.verticalCenter
text: qsTr("Experimental")
enabled: false
z: 0
rotation: -45
opacity: 0.1
font.pixelSize: 96
}

}

RowLayout {
id: buttonsRow
x: 0
y: parent.height - height
width: window.width

Button {
id: settingsButton
text: "☰"

onClicked: addResourcesPage.state = "EDITING_SETTINGS"
}

Button {
id: actionButton
text: "stuff"
visible: textArea.text || addResourcesPage.state ===
"EDITING_SETTINGS"
Layout.fillWidth: true
}
}
}
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] [ANNOUNCE] GammaRay 2.11.0

[Vadim Peretokin]

The Ubuntu 18.04 .deb does not seem to work:

vadi@volga:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
vadi@volga:~/Downloads$ sudo dpkg -i gammaray_2.11.0_amd64.deb
[sudo] password for vadi:
Selecting previously unselected package gammaray.
(Reading database ... 357335 files and directories currently installed.)
Preparing to unpack gammaray_2.11.0_amd64.deb ...
Unpacking gammaray (2.11.0) ...
dpkg: dependency problems prevent configuration of gammaray:
 gammaray depends on kdstatemachineeditor; however:
  Package kdstatemachineeditor is not installed.
 gammaray depends on libqt5quickwidgets5 (>= 5.5.0); however:
  Package libqt5quickwidgets5 is not installed.

dpkg: error processing package gammaray (--install):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.2) ...
Processing triggers for gnome-menus (3.13.3-11ubuntu1.1) ...
Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Errors were encountered while processing:
 gammaray
vadi@volga:~/Downloads$

On Fri, Jul 5, 2019 at 7:33 PM Allen Winter via Interest <
interest@qt-project.org> wrote:

> Announcing GammaRay 2.11.0
>
> Highlights of this Release:
> =
>  * Drop support for Qt 4 and Qt <= 5.4.
>  * Drop support for MSVC 2010 and MSVC 2012, as well as GCC < 4.8.
>  * Add support for more QtNetwork properties.
>  * Add new network operations monitoring tool.
>  * Fix inspection of QJson types.
>  * Add thread affinity check to the problem reporter.
>  * Add new event monitoring tool.
>  * Initial forward compatibility with Qt6 build system.
>  * Improved performance of the Qt Quick 2 inspector and the signal monitor.
>
> The source code can be found on GitHub at:
> https://github.com/KDAB/GammaRay
> Tarballs and zipballs for v2.11.0 are available from:
> https://github.com/KDAB/GammaRay/releases
>
> For Linux users:
>  * we provide pre-built packages for some popular distributions at:
> https://software.opensuse.org/package/gammaray
>
> For OSX users:
>  * we provide a homebrew recipe, see:
> https://github.com/KDAB/homebrew-tap
>
> For Windows users:
>  * you'll need to build from source
>
> GammaRay is a tool to poke around in a Qt-application and also to
> manipulate
> the application to some extent. GammaRay uses various DLL injection
> techniques to hook into an application at runtime and provide access to a
> lot of interesting information.
>
> For more information about GammaRay, please see:
>  * the KDAB GammaRay home page at http://www.kdab.com/gammaray
>  * the GammaRay wiki at https://github.com/KDAB/GammaRay/wiki
>  * the GammaRay User Manual at
> https://docs.kdab.com/gammaray-manual/latest/
>  * the GammaRay API doc at https://docs.kdab.com/gammaray/latest/
>
> --
> Allen Winter | allen.win...@kdab.com | Senior Software Engineer
> KDAB (USA) LLC, a KDAB Group company
> Tel. USA +1-866-777-KDAB(5322) ext3
> KDAB - The Qt, C++ and OpenGL Experts
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] notarizing builds for Mac - enabling hardened runtime

[Vadim Peretokin]

Thanks for this - mind pasting it as a gist for easy access?

On Wed, Jul 10, 2019 at 9:59 PM Elvis Stansvik  wrote:

> Den ons 10 juli 2019 kl 21:44 skrev Elvis Stansvik :
> >
> > Den ons 10 juli 2019 kl 21:20 skrev Adam Light :
> > >
> > >
> > >
> > > On Wed, Jul 10, 2019 at 2:28 AM Elvis Stansvik 
> wrote:
> > >>
> > >>
> > >> With "work around" do you mean from the user POV (e.g. somehow
> > >> disabling Gatekeeper, or Ctrl+Open, or something else) or from a
> > >> developer POV (so, having to notarize)?
> > >>
> > >
> > > Instead of repeating myself here, please see my comment at
> https://bugreports.qt.io/browse/QTBUG-73398?focusedCommentId=468111&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-468111
> which explains what I mean by "work around". I just added screen shots of
> the dialogs I mentioned in that comment so it's clear what the user sees.
> > >
> > >>
> > >> I'd like to know if there is some reasonably simple way for users to
> > >> get around the requirement. We will not be able to notarize every
> > >> build we do, because of the time it takes. But at the same time we,
> > >> and our testers, must be able to test random builds from Git (we build
> > >> a .dmg for every commit) to try out in-progress features/bug fixes...
> > >> So I really hope there will be some way for the user to get around the
> > >> notarization requirement.
> > >
> > >
> > > Notarization doesn't take more than a few minutes (in my limited
> experience) but it's a hassle to script the process. Your build machines
> and possibly your testers will not need to have a notarized application
> because, as I understand it, notarization is not required if the
> application does not have a quarantine flag. If it's been downloaded via a
> standard web browser, it should have the flag. But if it was built on the
> machine, or if it was transferred from another machine using something like
> curl, rsync, etc. then it is unlikely to have the quarantine flag.
> >
> > Yes, looking at our last tagged release build, the notarization step
> > took 3 minutes 58 seconds.That's a doubling of our normal build time
> > though, which is why we're hesitant to do it on every commit. That,
> > and also I guess Apple don't really want people doing this anyway.
> >
> > Our testers normally pull the build artifacts using their web browser,
> > so the downloaded .dmg will be quarantined. We could tell them to curl
> > it of course, but we'd like to keep it as simple as possible for them
> > to test a feature/bugfix in progress, and asking them to use a
> > dedicated download tool goes against that.
> >
> > Scripting the notarization wasn't the painful thing. I made a quick
> > Python script that does it, and it has worked fine since then. What
>
> This is the snippet, in case someone else finds it useful (note that
> the --primary-bundle-id flag to altool is hard-coded in the script, so
> you'll want to edit that):
>
> #!/usr/bin/env python3
> #
> # Notarize a file
> #
> # Usage: notarize-macos.py   
> #
>
> from argparse import ArgumentParser
> from subprocess import check_output
> from plistlib import loads
> from time import sleep
>
>
> def main():
> parser = ArgumentParser()
> parser.add_argument('username', help='Apple ID user')
> parser.add_argument('password', help='Apple ID password')
> parser.add_argument('path', help='File to be notarized (e.g. .dmg)')
> args = parser.parse_args()
>
> print('requesting notarization of {}...'.format(args.path))
>
> request_uuid = loads(check_output([
> 'xcrun',
> 'altool',
> '--notarize-app',
> '--primary-bundle-id', 'com.yourdomain.yourapp.dmg',
> '--username', args.username,
> '--password', args.password,
> '--file', args.path,
> '--output-format', 'xml'
> ]))['notarization-upload']['RequestUUID']
>
> for i in range(200):
> response = loads(check_output([
> 'xcrun',
> 'altool',
> '--notarization-info', request_uuid,
> '--username', args.username,
> '--password', args.password,
> '--output-format', 'xml'
> ]))
> if response['notarization-info']['Status'] == 'success':
> print('notarization succeeded, see
> {}'.format(response['notarization-info']['LogFileURL']))
> print('stapling notarization to {}'.format(args.path))
> print(check_output(['xcrun', 'stapler', 'staple',
> args.path]).decode('utf-8'))
> return
> if response['notarization-info']['Status'] == 'invalid':
> raise RuntimeError('notarization failed, response
> was\n{}'.format(response))
> sleep(3)
>
> raise RuntimeError('notarization timed out, last response
> was\n{}'.format(response))
>
>
> if __name__ == '__main__':
> main()
>
> > bothers me is if it will make it harder for our testers. I wish Apple
> > could state clearly whether the

[Interest] error: reference to 'byte' is ambiguous with C++17

[Vadim Peretokin]

I'm compiling my Qt application with C++17 on Windows with the Qt-provided
MinGW 7.3.0 and the Qt definition of a byte is conflicting with the new one
defined in the standard (http://wg21.link/p0298r3).

Here's a snippet of the issue: https://paste.ubuntu.com/p/Y73FRVqq2n/

Full build log:
https://ci.appveyor.com/project/Mudlet/mudlet/builds/26199708

What's the correct solution here?
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] error: reference to 'byte' is ambiguous with C++17

[Vadim Peretokin]

On Wed, Jul 24, 2019 at 11:38 AM Giuseppe D'Angelo via Interest <
interest@qt-project.org> wrote:

> Il 24/07/19 09:25, Vadim Peretokin ha scritto:
> > I'm compiling my Qt application with C++17 on Windows with the
> > Qt-provided MinGW 7.3.0 and the Qt definition of a byte is conflicting
> > with the new one defined in the standard (http://wg21.link/p0298r3).
> >
> > Here's a snippet of the issue: https://paste.ubuntu.com/p/Y73FRVqq2n/
> >
> > Full build log:
> > https://ci.appveyor.com/project/Mudlet/mudlet/builds/26199708
> >
> > What's the correct solution here?
>
> As your log shows, that (re)definition of "byte" is coming from a MinGW
> header, and not Qt.
>
> Given the definition in the Standard Library is in the namespace std,
> the only possibility for a clash is that there's a "using namespace
> std;" directive somewhere in your code (or in some other header you
> include; Qt does not have anything like that). The solution is, as
> usual, to drop such a directive.
>
> This is the other side of the coin for "using namespace" directives:
> when names are added to those namespaces they may clash against existing
> code, destroying the isolation that namespaces offer in the first place.
>
>
That was it! Thanks for the detailed explanation. Removing the 'using
namespace std;' did the trick.
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QStringView implementation for Qt 5.9?

[Vadim Peretokin]

On Thu, Jul 25, 2019 at 1:32 PM René J. V. Bertin  wrote:
>
> Took me a bit more trial & error than I thought, but here's something with 
> which
> almost all tests pass:
>
> github:RJVB/QEmuStringView


I think you meant https://github.com/RJVB/QEmuStringView - and thanks,
it looks interesting!
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt free software policy

[Vadim Peretokin]

Sorry but I'll ask the obvious question: you bet your entire business
without paying for a license?

Have I misunderstood you?

On Wed, 14 Aug. 2019, 7:01 pm David M. Cotter,  wrote:

> +1 on this
>
> i am in the process of porting my legacy project to Qt and am afraid that
> i’ve made the wrong choice.  i’m just one guy and i bet my whole business
> on the availability of what  i need from Qt under LGPL
>
> i’m already using a third party HTTP server so i’m not affected by this
> but it’s a worrying sign. I too agree that the HTTP server really should be
> LGPL.
>
> What’s going to happen? It’s taken me over a year’s worth of work to get
> this far with Qt and i’m only half done. did i make the wrong choice?
>
> -dave
>
> > On Aug 14, 2019, at 9:18 AM, Benjamin TERRIER 
> wrote:
> >
> > Hi everyone,
> >
> > Since we are talking about the future of Qt these days, I would like
> > to know The Qt Company free software policy with Qt.
> >
> > Today, most of Qt modules are released under 3 free software licenses:
> LGPLv3,
> > GPLv2 and GPLv3. Some modules are released only under GPLv3.
> > If my memory is good, these GPLv3-only modules are the ones which used to
> > be commercial-only modules (like Qt Charts).
> >
> > However, it seems to me that most, if not all (except Qt 3D), new Qt
> modules
> > are now being released only under GPLv3:
> >  - Network Auth
> >  - WebGL
> >  - WASM
> >  - Http Server
> >  - Lottie
> >  - Quick 3D
> >  - MQTT
> >
> > I understand that The Qt Company is only obligated to release new modules
> > under GPLv3 (because of the KDE agreement).
> > I understand also that The Qt Company business model is selling Qt
> licenses
> > and has no direct financial interests in releasing Qt under any other
> license.
> >
> > So I can understand that some modules, in particular those valuable for
> wealthy industrial companies,
> > are only released under GPLv3.
> > However, for some modules like HttpServer, it seems to be an odd choice.
> There are plenty
> > alternatives available under LGPL or more permissive licenses, so I do
> not see what
> > would be the loss of releasing it under LGPLv3.
> >
> > Also the fact that those modules are GPLv3 only is a problem when
> developing with other
> > components that are GPLv2 only (and not GPLv2+).
> >
> > So I would like that someone could officially confirm if all new modules
> will be
> > released under GPLv3 only. Or if it is something that is decided on a
> per module
> > basis.
> >
> > I believe that Qt users and contributors deserve to know what it The Qt
> Company
> > view on this.
> > Using an LGPLv3 framework is not the same thing as using a GPLv3
> framework
> > where some historical parts are available under LGPLv3 and all new
> features will be GPLv3 only.
> >
> > BR,
> >
> > Benjamin
> >
> >
> > ___
> > Interest mailing list
> > Interest@qt-project.org
> > https://lists.qt-project.org/listinfo/interest
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt free software policy

[Vadim Peretokin]

Still, it reads like the Instagram influencer argument: "Give me free stuff
and I'll get you exposure.", and we all know how silly that sounds like.

On Thu, Aug 15, 2019 at 6:17 AM Tuukka Turunen  wrote:

>
>
> “This is wrong to say that the only alternative to Commercial + GPLv3 is
> Commercial only.”
>
>
>
> I did not say the _*only*_ alternative. Some new things are LGPL exactly
> to grow the user base. Qt for Python being one of such.
>
>
>
> Yours,
>
>
>
> Tuukka
>
>
>
> *From: *Benjamin TERRIER 
> *Date: *Wednesday, 14 August 2019 at 22.18
> *To: *Tuukka Turunen 
> *Cc: *qt qt 
> *Subject: *Re: [Interest] Qt free software policy
>
>
>
>
>
>
>
> Le mer. 14 août 2019 à 20:36, Tuukka Turunen  a
> écrit :
>
>
>
> Hi,
>
>
>
> Qt’s approach to open-source is publicly described, but perhaps a bit
> hidden, check for example:
>
> · Section 3 of https://www.qt.io/faq/
>
> · https://wiki.qt.io/Qt_Project_Open_Governance
>
> · https://www.qt.io/licensing/
>
>
>
> These pages are just presenting the current licensing options.
>
> They do not cover how The Qt Company view the licensing of future Qt
> modules.
>
>
>
> We have been releasing new add-on modules under GPLv3 and commercial
> licenses with intention of growing the adoption of commercial license for
> those making closed-source applications with Qt. Alternative for using
> GPLv3 and commercial would be to only offer these add-ons separately under
> a commercial license, which would mean not even those who are ok with GPLv3
> license could use these add-ons. Some of such components do exist, but most
> of our code is available under an open-source license as well.
>
>
>
> This is wrong to say that the only alternative to Commercial + GPLv3 is
> Commercial only.
>
> The new add-ons modules could be provided as GPLv3 + GPLv2 + LGPLv3.
>
> I understand the will to grow "the adoption of commercial license", but I
> believe that some modules which have a lot of alternatives available could
> be licensed also under GPLv2 and/or LPGLv3 without going against "the
> adoption of commercial license".
>
> Also having more module on LGPL can grow the Qt community leading to
> indirect sales of the commercial license.
>
>
>
> For instance when I work on GPLv3 projects I can use all Qt add-ons, but
> when I work on GPLv2 or LGPLv3 project I cannot use the most recent Qt
> modules.
>
> Which means that I have to find an alternative anyway. In the end I do not
> use these Qt add-ons, even for the GPLv3 projects as I have an alternative
> ready.
>
>
>
> At the same time we have developed a lot of new functionality, done a lot
> of improvements, and fixed a lot of bugs in functionality available also
> with LGPL license. This is a big investment, which directly benefits all Qt
> users whether they distribute their applications under LGPL, GPL or
> commercial license. Just look at the amount of new and changed code and you
> can see that the LGPLv3 parts are clearly not some legacy functionality,
> but very actively developed areas of Qt.
>
>
>
> I am not denying that.
>
> It is just that all the novelties are GPLv3 only and I think it should be
> made clear to the community that new LGPL modules are not to be expected.
>
>
>
> BR
>
>
>
> Benjamin
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt free software policy

[Vadim Peretokin]

Which was actually a very, very bad surprise that was pretty poorly
documented. Please don't do that again.

We saw the openssl change and didn't think anything big of it - well, it
turned out that a minor upgrade to an TLS release completely broke secure
web downloads, secure TLS connections, and our updater: so our software
self-upgraded to a version it can't self-upgrade from. Horribly nasty
experience all in all :( there should have been a bigger warning on this.

On Mon, Aug 19, 2019 at 2:06 AM Hamish Moffatt 
wrote:

> On 15/8/19 6:28 am, Thiago Macieira wrote:
> > PS: Qt 5.12 will switch to OpenSSL 1.1 in the binary builds.
>
>
> Indeed 5.12.4 already did.
>
>
>
> Hamish
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] mac app crashes if you plug in another monitor

[Vadim Peretokin]

The mailing list isn't appropriate for complaints. File a bug report like
everyone else, or contact your Qt support if you're on the commercial
edition. Thanks!

On Fri, 13 Sep. 2019, 5:24 pm David M. Cotter,  wrote:

> *I* am not doing anything.  this is the Qt framework
>
> On Sep 13, 2019, at 8:01 AM, Jérôme Godbout  wrote:
>
> Are you updating the CocoaScreen from a different thread then the main
> main thread?
>
>
> *From:* Interest  *On Behalf Of *David
> M. Cotter
> *Sent:* September 13, 2019 10:49 AM
> *To:* Interest 
> *Subject:* [Interest] mac app crashes if you plug in another monitor
>
> this seems unexpected
>
> 
>
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] Dark mode for other platforms

[Vadim Peretokin]

Hello!

I've noticed that Qt on macOS now automatically uses dark mode, and it
looks amazing
. My
question is: how can I enable this for Windows and Linux as well?

Thanks!
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Dark mode for other platforms

[Vadim Peretokin]

But Qt on Windows doesn't automatically obey this dark mode like it does on
macOS - is there anything I can do to nudge it that way?
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Dark mode for other platforms

[Vadim Peretokin]

No problem! Thanks for the answer.

In the meantime we can use stylesheets for this:
https://github.com/ColinDuquesnoy/QDarkStyleSheet

On Wed, Oct 16, 2019 at 2:44 PM Mårten Nordheim 
wrote:

> On 16.10.2019 14:38, Vadim Peretokin wrote:
> > But Qt on Windows doesn't automatically obey this dark mode like it does
> > on macOS - is there anything I can do to nudge it that way?
>
> Unfortunately not, it just hasn’t been implemented in Qt yet for various
> reasons.
>
> Although there has been some work on it recently by Friedemann
> https://codereview.qt-project.org/c/qt/qtbase/+/275191
> https://bugreports.qt.io/browse/QTBUG-72028
>
> Mårten
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] WebAssembly - QtCreator device support on MacOS

[Vadim Peretokin]

On Mon, Nov 18, 2019 at 5:35 PM Boris Ralchenko  wrote:

> Good day,
>
> I don’t see WebAssembly in Device support plugins in Qt Creator, I just
> installed Qt 5.13.2 on the latest MacOS.  The toolchain seems to work, but
> I can’t really build anything with Qt Creator. The instructions are here
> https://doc-snapshots.qt.io/qtcreator-master/creator-setup-webassembly.html
>
> Is it supported on MacOS at all?
>
> Regards,
> Boris Ralchenko.
>


What error are you getting?
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] WebAssembly - QtCreator device support on MacOS

[Vadim Peretokin]

Install the latest preview of Qt Creator.

On Mon, Nov 18, 2019 at 8:04 PM Boris Ralchenko  wrote:

> No errors, plugin for webAssembly is not there..
>
>
>
> and build fails, as expected
> no symbols
> wasm-ld: error: main.o: machine type must be wasm32
> wasm-ld: error: moc_main.o: machine type must be wasm32
> wasm-ld: error: main.o: machine type must be wasm32
> wasm-ld: error: moc_main.o: machine type must be wasm32
> wasm-ld: error: moc_main.o: machine type must be wasm32
> wasm-ld: error: main.o: machine type must be wasm32
>
> Regards,
> Boris Ralchenko.
>
>
>
>
>
> On Nov 18, 2019, at 1:25 PM, Vadim Peretokin  wrote:
>
>
> On Mon, Nov 18, 2019 at 5:35 PM Boris Ralchenko 
> wrote:
>
>> Good day,
>>
>> I don’t see WebAssembly in Device support plugins in Qt Creator, I just
>> installed Qt 5.13.2 on the latest MacOS.  The toolchain seems to work, but
>> I can’t really build anything with Qt Creator. The instructions are here
>> https://doc-snapshots.qt.io/qtcreator-master/creator-setup-webassembly.html
>>
>> Is it supported on MacOS at all?
>>
>> Regards,
>> Boris Ralchenko.
>>
>
>
> What error are you getting?
>
>
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Cross-platform local notifications?

[Vadim Peretokin]

For Mac/win/Linux? That'd be amazing if you could share it.

On Wed, 11 Mar. 2020, 2:53 am Jason H,  wrote:

> Qt does not. But I do... I'm not at my source atm though..
>
> > Sent: Monday, March 09, 2020 at 9:36 PM
> > From: "Israel Brewster" 
> > To: "Jérôme Godbout" 
> > Cc: Interest 
> > Subject: Re: [Interest] Cross-platform local notifications?
> >
> > For iOS specifically I’m talking about this:
> >
> >
> https://developer.apple.com/design/human-interface-guidelines/ios/system-capabilities/notifications/
> <
> https://developer.apple.com/design/human-interface-guidelines/ios/system-capabilities/notifications/
> >
> >
> > Which may or may not be the same as the link you just sent :-) I’m
> assuming Android has something similar, but the link you sent has a note at
> the top stating "This package is part of the Android support library which
> is no longer maintained” - presumably there is something that *is* still
> maintained.
> >
> >
> > But yeah, I’m looking (hoping?) for a Qt common abstraction. Otherwise,
> I guess I’ll have to write native and tie it in somehow…. Not sure how that
> works for android.
> > ---
> > Israel Brewster
> > Software Engineer
> > Alaska Volcano Observatory
> > Geophysical Institute - UAF
> > 2156 Koyukuk Drive
> > Fairbanks AK 99775-7320
> > Work: 907-474-5172
> > cell:  907-328-9145
> >
> > > On Mar 9, 2020, at 12:32 PM, Jérôme Godbout 
> wrote:
> > >
> > > What you describe look like a local notification (not pushed), for iOS
> > >
> https://developer.apple.com/library/archive/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/SchedulingandHandlingLocalNotifications.html
> <
> https://developer.apple.com/library/archive/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/SchedulingandHandlingLocalNotifications.html
> >
> > >
> > > for Android you might want to take a look at NotificationCompat.Builder
> > >
> https://developer.android.com/reference/android/support/v4/app/NotificationCompat.Builder
> <
> https://developer.android.com/reference/android/support/v4/app/NotificationCompat.Builder
> >
> > >
> > > I don’t known if any Qt common layer is made for those!?
> > >
> > >
> > > From: Interest  On Behalf Of Israel
> Brewster
> > > Sent: March 9, 2020 4:22 PM
> > > To: Interest 
> > > Subject: [Interest] Cross-platform local notifications?
> > >
> > > I’m writing a Qt C++ (not QML) app for iOS and android, and I need to
> be able to display a notification (such that would show up in Notification
> Center on iOS, not an alert box). How can I do this? My searches on google
> only find results for push notifications (this is all local) or maybe an
> implementation in QML.
> > >
> > > ---
> > > Israel Brewster
> > > Software Engineer
> > > Alaska Volcano Observatory
> > > Geophysical Institute - UAF
> > > 2156 Koyukuk Drive
> > > Fairbanks AK 99775-7320
> > > Work: 907-474-5172
> > > cell:  907-328-9145
> >
> > ___
> > Interest mailing list
> > Interest@qt-project.org
> > https://lists.qt-project.org/listinfo/interest
> >
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] OSX codesign question

[Vadim Peretokin]

You might be missing some magical commands to import the identity - check
out
https://github.com/Mudlet/Mudlet/blob/development/CI/travis.osx.after_success.sh#L17
for an example.
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Windows installer for Qt programs

[Vadim Peretokin]

Hello,

If you're targeting normal users and not sysadmins, I'd recommend Squirrel
instead: https://github.com/Squirrel/Squirrel.Windows

Qt Installer Framework works but it has aesthetics targeting 2010, not 2020.

On Tue, Apr 21, 2020 at 9:37 AM Dmitriy Purgin  wrote:

> Hello Alexander,
>
> you could try Qt Installer Framework:
> https://doc.qt.io/qtinstallerframework/index.html
>
> Cheers
> Dmitriy
>
> On Tue, Apr 21, 2020 at 9:20 AM "Alexander Carôt" 
> wrote:
>
>> Hello all,
>>
>> I consider shipping my Qt built software with a conventional installer on
>> Windows.
>>
>> Can anyone give me a recommendation of a solid freeware for this purpose ?
>>
>> Thanks in advance,
>> best
>>
>> Alex
>>
>> --
>> http://www.carot.de
>> Email : alexan...@carot.de
>> Tel.: +49 (0)177 5719797
>>
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> https://lists.qt-project.org/listinfo/interest
>>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] [Development] Windows 7 support will be dropped in Qt 6

[Vadim Peretokin]

At the end of the day it is the commercial contracts that the Qt company
has that fund the development of Qt. If you have one, make sure to reach
out on the appropriate channels.

If you don't have one, get one, so you have a voice.
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] Set manipulation in Qt 6

[Vadim Peretokin]

Being good users open-source of Qt, we're 
looking into our compatibility early on to help report any issues and we're
finding this compatibility code to be rather problematic from the developer
experience point of view:

QMap> customLines;
QMap customLinesColor;
// ...

#if (QT_VERSION >= QT_VERSION_CHECK(5, 14, 0))
auto customLineKeys = customLines.keys();
QSet missingKeys{customLineKeys.begin(), customLineKeys.end()};
if (!customLinesColor.isEmpty()) {
auto customLinesColorKeys = customLinesColor.keys();
QSet customLinesColorKeysSet{customLinesColorKeys.begin(),
customLinesColorKeys.end()};
missingKeys.subtract(customLinesColorKeysSet);
}
#else
QSet
missingKeys{customLines.keys().toSet().subtract(customLinesColor.keys().toSet())};
#endif

Are we doing it wrong or is this a regression in Qt? (QTBUG-83697
)
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] Qt Installer for Windows: installs broken compiler

[Vadim Peretokin]

While I've previously had MinGW 32bit installed by Qt working fine, this is
no longer the case with the latest 5.12 LTS and Qt Online Installer
combination:

[image: Workspace 1_491.png]
Trying to compile something results in a "Maybe you forgot to setup the
environment?". Everything is setup in the online installer fine:

[image: image.png]
What could be the problem?
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt Installer for Windows: installs broken compiler

[Vadim Peretokin]

On Tue, Dec 1, 2020 at 10:43 AM Christian Kandeler 
wrote:

> On 12/1/20 10:26 AM, Vadim Peretokin wrote:
> > While I've previously had MinGW 32bit installed by Qt working fine,
> > this is no longer the case with the latest 5.12 LTS and Qt Online
> > Installer combination:
>
>
> The tooltip you are seeing appears if the compiler executable either
> does not exist or is not an executable file, so you might want to check
> that.
>
> I just installed this particular compiler from the installer and do not
> observe this behavior.
>
>
Thanks for the tip, that was the issue. I previously renamed the directory
it is installed in and forgot about that. It's interesting that
reinstalling the compiler did not restore the directory!



>
> Christian
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] Squish for open source

[Vadim Peretokin]

Following the news that Qt has acquired the excellent UI-based testing
software Squish (https://www.qt.io/blog/quality-assurance-tools), could
that offering be extended to open source projects by QtC?

There's no real alternatives that I know of that can do UI-based testing
for Qt Widgets projects - or if I haven't looked hard enough, happy to hear
suggestions.

Best regards,
Vadim.
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Squish for open source

[Vadim Peretokin]

It doesn't look to have any proper maintenance since 2017 and lacks plans
for Qt6, so that doesn't look like a viable option to invest lots of effort
into.

Given the recent bad press for Qt regarding open-source, QtC opening up
Squish for open-source use would definitely be some good news.

On Tue, Apr 20, 2021 at 9:56 AM Michal Lazo  wrote:

> Hello
> If you are looking for something for qt widgets application there is
> alternative for example this
> https://github.com/cisco-open-source/qtwebdriver
>
> Best regards
> Michal Lazo
>
> On Mon, Apr 19, 2021 at 3:20 PM Vadim Peretokin 
> wrote:
> >
> > Following the news that Qt has acquired the excellent UI-based testing
> software Squish (https://www.qt.io/blog/quality-assurance-tools), could
> that offering be extended to open source projects by QtC?
> >
> > There's no real alternatives that I know of that can do UI-based testing
> for Qt Widgets projects - or if I haven't looked hard enough, happy to hear
> suggestions.
> >
> > Best regards,
> > Vadim.
> > ___
> > Interest mailing list
> > Interest@qt-project.org
> > https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] Qt4 Retina support

[Vadim Peretokin]

Hi,

What is the current status of Retina support with Qt4?

I found https://github.com/msorvig/qt4-hidpi, the bugreport and the plist
suggestions - but it's not clear as to what one should do to fix the
blurriness (and unsuitability) of apps.

Can anyone recap the status of Retina support?
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt4 Retina support

[Vadim Peretokin]

Thank you
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Please recommend some editor widgets

[Vadim Peretokin]

There is QScintilla as well, but I can't say I can recommend it as I
remember it having internalization issues. Maybe it has been fixed since,
that was a while ago.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QtCreator, Mac OSX and LLDB?

[Vadim Peretokin]

Have you reported this information anywhere else at all, especially on the
bugtracker, since you've started experiencing these problems?
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Shadow problem after hiding/removing window decorations. ( Linux/Ubuntu )

[Vadim Peretokin]

I think it's the window manager (compiz if you're using 3D, metacity if
you're using 2D) that is applying the shadows - not Qt. There might or
might not be a way to signal it which kind of shadows to use, I'm not
certain.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Compiling Programs with C++11 with Qt5, which was compiled without C++11 flag. Possible?

[Vadim Peretokin]

No, screenshots of code are not prefered on SO and no, Ubuntu does not go
out and hack things just to break them and cause misery. That's not why
they're popular :)
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Native text rendering in Qt 5.1 on Windows

[Vadim Peretokin]

I can confirm the visual regression in font rendering on Linux with Qt 5.x (
report1 ,
report2
).

Thanks Mark for the tips on fiddling with it, I'll definitely give that a
go.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Calling QSettings::value() with an empty key name triggers an assert

[Vadim Peretokin]

He's wanting to *set* the key to the default value however, not access it.
Unless QSettings::value(".") or QSettings::value("Default") will set it to
the default value as you suggest?
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Calling QSettings::value() with an empty key name triggers an assert

[Vadim Peretokin]

Got it, thanks.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] bug with Qt example --draggableicons

[Vadim Peretokin]

Which OS are you on?
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QTreeView header move first column doesn't work.

[Vadim Peretokin]

I can confirm this problem - please share the bug URL you file.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Undesired space added in Mac style UI rendering

[Vadim Peretokin]

I'll try those two flags... if you mention it looks different for you,
would you mind showing me a screenshot of how it looks for you? I've just
got this one mac (and it's not even a real one) to help Mac users with.


On Tue, Nov 5, 2013 at 5:26 AM, John Weeks  wrote:

> Agh... once again, I forgot to direct my answer to the list.
>
>
> Well, I'm not sure of the solution, but the extra space appears to be
> coming from the checkbox used as the groupbox title. In your screen shots,
> the checkbox text is the same size as the other groupbox titles, on my
> Macintosh running 10.6.8 (out of date...) the checkbox text is actually
> larger than the other titles.
>
> This seems like a bug in the Macintosh style; on my machine the checkmark
> (which extends beyond the checkmark box) is truncated. At the very least,
> it seems like the gap should be filled in with the groupbox background.
> Also, if I set the palettes to the default, the background appears to fill
> the space better. It looks like the Macintosh style is not measuring the
> space required for the checkbox correctly in all parts of its code.
>
> You might try setting QWidget:: setAttribute(Qt::WA_MacSmallSize)
> or  setAttribute(Qt::WA_MacMiniSize). I haven't found a way to set these
> attributes other than in code. It would be nice if there were an obvious
> way to set them in Designer.
>
> -John Weeks
>
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Undesired space added in Mac style UI rendering

[Vadim Peretokin]

Thanks. I'll see what I can do about it in the code then.

Yes, possibly - but given how this is a cross-platform application and I
have seen users use many OSes in their daily use, I think we would have
questions to us raised if we didn't colour them as we equally did on the
other platforms. What I mean to say is I think there are less purists out
there than common users who would think we did a poorer job on the Macs.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] "Current" guide to deploying Qt applications on OSX

[Vadim Peretokin]

Hi,

I'm in the process of learning / deploying a Qt application on Mac, and
I've got several questions about the process - since the official "Deploying
an Application on Mac OS
X"
guide not quite clear[1].

The documentation for the
macdeployqttool
says "Note: If you want a 3rd party library to be included in your
application bundle, you must copy the library into the bundle manually,
after the bundle is created.". However, in my case, it seems to have
included the 3rd party libraries into the bundle automatically - for
example, my application links to Lua, and when my .app is created, appears.
So whom can I trust - does macdeployqt now properly supports 3rd party
libraries, and the documentation is wrong? Or the documentation is right,
and whatever macdeployqt did, I can't trust yet for mass deployment?

The second question is in regards to the application name when the -dmg
option is used - it is in lowercase when the .dmg file is opened. What is
the kosher way to change it - would just changing the filename of the .app
going in be fine?

Lastly, I've seen customizations on the .dmg window where a custom
background was added. Is this possible to do in harmony with macdeployqt,
or is it accomplished via some other method?

Thanks!

[1] - it seems to be a guide in great need of refactoring, having existed
in its basic form all the way from Qt 3.0 / OSX
10.2 with
more and more bits tacked on top; which also since Qt 4.5 essentially says
at the top "ignore 90% of this file, skip down to the bottom 10%".
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] "Current" guide to deploying Qt applications on OSX

[Vadim Peretokin]

Got it. Thanks for the prompt reply!
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] How to show window list for

[Vadim Peretokin]

When I open multiple windows in my Qt4 app on mac, the toolbar lists them:
https://i.stack.imgur.com/l7jCp.png

When I do the same in Qt5, the toolbar doesn't list any windows my
application has: https://i.stack.imgur.com/EI0RV.png

This is a serious issue since if the user minimises a window from the
application, and minimize to dock icon

 is enabled, the only way to bring the window back is to use "show all
windows" menu.

I've looked around but couldn't find an option, and I noticed that Tiled,
another Qt app, also suffers from this problem on macOS. How can I fix this?
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] How to show window list for

[Vadim Peretokin]

Anyone have any ideas? I've had a look and as far as I see, every Qt5
application on macOS suffers from this bug and will assume so unless proven
otherwise. I've filed https://bugreports.qt.io/browse/QTBUG-59433.

On Mon, Mar 6, 2017 at 8:14 PM Vadim Peretokin  wrote:

> When I open multiple windows in my Qt4 app on mac, the toolbar lists them:
> https://i.stack.imgur.com/l7jCp.png
>
> When I do the same in Qt5, the toolbar doesn't list any windows my
> application has: https://i.stack.imgur.com/EI0RV.png
>
> This is a serious issue since if the user minimises a window from the
> application, and minimize to dock icon
> <https://www.howtogeek.com/285750/how-to-set-macos-applications-to-minimize-to-their-dock-icon/>
>  is enabled, the only way to bring the window back is to use "show all
> windows" menu.
>
> I've looked around but couldn't find an option, and I noticed that Tiled,
> another Qt app, also suffers from this problem on macOS. How can I fix this?
>
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Qt internalisation support for C++11 raw literals

[Vadim Peretokin]

Is anyone running a C++ project that does their translation with Qt? I'm
having trouble with lupdate barfing on raw literals and found a
corresponding bug report  on
it.

I find it hard to believe that the "most widely used C++ framework" doesn't
support raw literals in i18n 6 years after the standard was released, so I
hope I'm in the wrong on this.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QDockWidgets: how to get regular windows in detached (floating) mode?

[Vadim Peretokin]

Rene, with the thing you're making - would it then be possible to achieve
browser-like behaviour of being able to drag tabs out into their own
windows? With those windows movable to other monitors as well?

On Thu, Oct 12, 2017 at 11:05 AM René J. V. Bertin 
wrote:

> John Weeks wrote:
>
> > You may need to call setVisible(true). IIRC, changing window flags makes
> the
> > widget invisible.
>
> You appear to be right, thanks.
>
> Now I'm just left with how to restore state correctly after starting the
> application anew. After unfloating the window with
>
> static void unfloat(QDockWidget* that, bool floating)
> {
> if (floating && that) {
> that->setTitleBarWidget(0);
> // remove unwanted flags
> Qt::WindowFlags flags = that->windowFlags() & ~(Qt::Tool|
> Qt::FramelessWindowHint|Qt::X11BypassWindowManagerHint);
> // set wanted flags
> that->setWindowFlags(flags | Qt::Window);
> that->updateGeometry();
> that->setVisible(true);
> }
> }
>
> I'm stuck with a window that just shows whatever was behind it when it was
> first
> created.
>
> Maybe I should un-unfloat the window before exiting, or simply dock it.
>
> R.
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QDockWidgets: how to get regular windows in detached (floating) mode?

[Vadim Peretokin]

Are you using QToolBar? The only thing those can do is move around in the
tab bar, but they can't be dragged out...

I'd love to have browser-like functionality where you could drag those tabs
out as well which is why I'm so keen on what you're doing here!

On Thu, Oct 12, 2017 at 12:27 PM René J.V. Bertin 
wrote:

> On Thursday October 12 2017 09:06:52 Vadim Peretokin wrote:
>
> >Rene, with the thing you're making - would it then be possible to achieve
> >browser-like behaviour of being able to drag tabs out into their own
> >windows?
>
> Not for any kind of tab of course, only those that are usually docked to a
> toolbar on one of the window edges. You can already drag them out into
> their own window, but those don't behave like standard windows.
>
> >With those windows movable to other monitors as well?
>
> On Mac I can already do that with QDockWidgets in floating mode, doesn't
> it work like that on other platforms?
>
> R.
>
>
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QT 5.9.2 Print Dialog

[Vadim Peretokin]

Are you using the windeployqt to create a deployment version of your app?

On Mon, Oct 23, 2017 at 9:17 AM Sudhir Sharma 
wrote:

> Hi,
>
>
>
> I am facing a strange problem, where I am able to invoke Print Dialog from
> my development machine(windows 8).
>
> But when I install my application in difference machine (win 10), the
> Print Dialog does not show up.
>
>
>
> Seems to be issue of missing or wrong DLLs in other machine.
>
> I have checked for “Qt5PrintSupport.dll”, which is same in both machines.
>
>
>
> Any idea what else could be wrong?
>
>
>
> Regards,
>
> Sudhir
>
> --
>
> http://www.mindtree.com/email/disclaimer.html
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] minimum macOS runtime version for Qt 5.9+

[Vadim Peretokin]

I don't know where you're looking, but that says Linux is at 2.98% while
macOS 10.10 is at 0.75%. Just pointing it out in case someone else believed
this at first.

On Wed, Nov 29, 2017 at 9:24 AM Jean-Michaël Celerier <
jeanmichael.celer...@gmail.com> wrote:

> There are more or less as many MacOS 10.10 users than Linux users
> apparently, so by that logic Qt should be dropping Linux support altogether
> :p (according to https://www.netmarketshare.com/)
>
>
>
> ---
> Jean-Michaël Celerier
> http://www.jcelerier.name
>
> On Wed, Nov 29, 2017 at 4:46 AM, Jake Petroules 
> wrote:
>
>>
>>
>> > On Nov 28, 2017, at 7:43 PM, Hamish Moffatt 
>> wrote:
>> >
>> > https://doc.qt.io/qt-5/supported-platforms.html lists the supported
>> macOS environments, but it's not clear if it's the same versions (10.10+)
>> for runtime (deployment) as well as development, or whether running on
>> earlier versions is supported. Does anyone know?
>>
>> Currently we support the same minimum version for both runtime and
>> development. Currently this is macOS 10.10 for Qt 5.9. Earlier OS versions
>> will not work and will crash.
>>
>> > http://doc-snapshots.qt.io/qt5-5.10/supported-platforms.html suggests
>> that 5.10 will increase this requirement further to 10.11+. Why is this?
>>
>> We decided it wasn't worth the resources to continue testing with 10.10.
>> macOS upgrades are now free and the overwhelming majority of users are on
>> the latest version.
>>
>> Why do you need to support older versions?
>>
>> > Thanks,
>> >
>> > Hamish
>> >
>> > ___
>> > Interest mailing list
>> > Interest@qt-project.org
>> > http://lists.qt-project.org/mailman/listinfo/interest
>>
>> --
>> Jake Petroules - jake.petrou...@qt.io
>> The Qt Company - Silicon Valley
>> Qbs build tool evangelist - qbs.io
>>
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
>>
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] minimum macOS runtime version for Qt 5.9+

[Vadim Peretokin]

Well you haven't shown your search criteria but I can tell you that the
October 2017 stats are not what you say: https://imgur.com/a/avGLj. If
you're gonna be using stats to reinforce your point, you've gotta be honest
about it.

On Wed, Nov 29, 2017 at 9:47 AM Jean-Michaël Celerier <
jeanmichael.celer...@gmail.com> wrote:

> Uh ? For me it says 2.20% for MacOS 10.10 and 1.75% for Linux (in Desktop
> OS market share).
> https://imgur.com/a/xvAzX
>
>
>
> ---
> Jean-Michaël Celerier
> http://www.jcelerier.name
>
> On Wed, Nov 29, 2017 at 9:28 AM, Vadim Peretokin 
> wrote:
>
>> I don't know where you're looking, but that says Linux is at 2.98% while
>> macOS 10.10 is at 0.75%. Just pointing it out in case someone else
>> believed this at first.
>>
>> On Wed, Nov 29, 2017 at 9:24 AM Jean-Michaël Celerier <
>> jeanmichael.celer...@gmail.com> wrote:
>>
>>> There are more or less as many MacOS 10.10 users than Linux users
>>> apparently, so by that logic Qt should be dropping Linux support altogether
>>> :p (according to https://www.netmarketshare.com/)
>>>
>>>
>>>
>>> ---
>>> Jean-Michaël Celerier
>>> http://www.jcelerier.name
>>>
>>> On Wed, Nov 29, 2017 at 4:46 AM, Jake Petroules 
>>> wrote:
>>>
>>>>
>>>>
>>>> > On Nov 28, 2017, at 7:43 PM, Hamish Moffatt <
>>>> ham...@risingsoftware.com> wrote:
>>>> >
>>>> > https://doc.qt.io/qt-5/supported-platforms.html lists the supported
>>>> macOS environments, but it's not clear if it's the same versions (10.10+)
>>>> for runtime (deployment) as well as development, or whether running on
>>>> earlier versions is supported. Does anyone know?
>>>>
>>>> Currently we support the same minimum version for both runtime and
>>>> development. Currently this is macOS 10.10 for Qt 5.9. Earlier OS versions
>>>> will not work and will crash.
>>>>
>>>> > http://doc-snapshots.qt.io/qt5-5.10/supported-platforms.html
>>>> suggests that 5.10 will increase this requirement further to 10.11+. Why is
>>>> this?
>>>>
>>>> We decided it wasn't worth the resources to continue testing with
>>>> 10.10. macOS upgrades are now free and the overwhelming majority of users
>>>> are on the latest version.
>>>>
>>>> Why do you need to support older versions?
>>>>
>>>> > Thanks,
>>>> >
>>>> > Hamish
>>>> >
>>>> > ___
>>>> > Interest mailing list
>>>> > Interest@qt-project.org
>>>> > http://lists.qt-project.org/mailman/listinfo/interest
>>>>
>>>> --
>>>> Jake Petroules - jake.petrou...@qt.io
>>>> The Qt Company - Silicon Valley
>>>> Qbs build tool evangelist - qbs.io
>>>>
>>>> ___
>>>> Interest mailing list
>>>> Interest@qt-project.org
>>>> http://lists.qt-project.org/mailman/listinfo/interest
>>>>
>>>
>>> ___
>>> Interest mailing list
>>> Interest@qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/interest
>>>
>>
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] minimum macOS runtime version for Qt 5.9+

[Vadim Peretokin]

This sounds like a commercial issue then, could this be discussed on the
official commercial channels instead?

On Wed, Nov 29, 2017 at 2:09 PM coroberti .  wrote:

> On Wed, Nov 29, 2017 at 2:22 PM, Hamish Moffatt
>  wrote:
> > On 29/11/17 14:46, Jake Petroules wrote:
> >>
> >> Why do you need to support older versions?
> >
> > Because my customers are using them, right back to 10.7. They are
> > educational institutions with whole labs of machines set up the same way
> -
> > they probably get one chance a year to upgrade, and for whatever reason
> they
> > haven't so far. I can't stick to old Qt versions either because of
> various
> > bugs. 5.6 LTS has issues with accessibility crashes on newer macOS. 5.8
> is
> > crashing in file open dialogs on 10.13. Thus I'm stuck.
>
> Exactly, my case with edu users.
> They are using Mac HW for up to 10 years.
> About 1/3 is not upgradeable anymore: 10.7 and 10.8
>
> > I wish there was a bit more of a time window before you deprecate old
> > versions. 10.7 is no older than Windows 7.
>
> +1
>
> Kind regards,
> Robert
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Is this a know issue? -> Thread 0 Crashed -> CreateFontWithFontURL(__CFURL const*, bool) + 412

[Vadim Peretokin]

Have you tried searching the place where known issues are listed - the bug
tracker?

On Thu, 30 Nov 2017, 1:23 pm Nuno Santos,  wrote:

> Hi,
>
> I have recently update an app to use Qt 5.9.2 on Mac OSX.
>
> Some users are having this crash stack trace.
>
> Is this a known issue?
>
> Regards,
>
> Nuno
>
> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
> 0 com.apple.CoreFoundation 0x7fff87461acf _CFRetain + 63
> 1 com.apple.CoreText 0x7fff86a9406c
> CreateFontWithFontURL(__CFURL const*, bool) + 412
> 2 com.apple.CoreText 0x7fff86a93d2b
> TCGFontCache::CopyFont(__CFURL const*, bool) const + 91
> 3 com.apple.CoreText 0x7fff86a93b55 TBaseFont::CopyNativeFont()
> const + 69
> 4 com.apple.CoreText 0x7fff86a93ad6
> TBaseFont::CopyGraphicsFont() const + 26
> 5 com.apple.CoreText 0x7fff86a937ec
> TBaseFont::CopyTable(unsigned int) const + 188
> 6 com.apple.CoreText 0x7fff86aa581c
> TBaseFont::CreateTraitsValuesPerFontInfo() const + 1140
> 7 com.apple.CoreText 0x7fff86aa52af TBaseFont::CopyTraitsInternal()
> const + 87
> 8 com.apple.CoreText 0x7fff86aa4e3d
> TBaseFont::CopyAttribute(unsigned long) const + 493
> 9 com.apple.CoreText 0x7fff86a92eb1
> TDescriptor::CopyAttribute(__CFString const*) const + 175
> 10 com.apple.CoreText 0x7fff86a92ddf CTFontDescriptorCopyAttribute
> + 99
> 11 libqcocoa.dylib 0x000111e13beb 0x111da + 474091
> 12 libqcocoa.dylib 0x000111e13298 0x111da + 471704
> 13 libqcocoa.dylib 0x000111e1646f 0x111da + 484463
> 14 org.qt-project.QtGui 0x00010f7fbbaf 0x10f71 + 965551
> 15 org.qt-project.QtGui 0x00010f7fb9b2 0x10f71 + 965042
> 16 org.qt-project.QtGui 0x00010f7fbe53
> QFontDatabase::addApplicationFont(QString const&) + 227
> 17 org.qt-project.QtQuick 0x00010e95bdc9 0x10e912000 + 302537
> 18 org.qt-project.QtQml 0x00010eef448a 0x10ecb4000 + 2360458
> 19 org.qt-project.QtQml 0x00010eef553e 0x10ecb4000 + 2364734
> 20 org.qt-project.QtQml 0x00010eef222f 0x10ecb4000 + 2351663
> 21 org.qt-project.QtQml 0x00010eef6a4d 0x10ecb4000 + 2370125
> 22 org.qt-project.QtQml 0x00010eef172f 0x10ecb4000 + 2348847
> 23 org.qt-project.QtQml 0x00010eef4f79 0x10ecb4000 + 2363257
> 24 org.qt-project.QtQml 0x00010eef222f 0x10ecb4000 + 2351663
> 25 org.qt-project.QtQml 0x00010eef6a4d 0x10ecb4000 + 2370125
> 26 org.qt-project.QtQml 0x00010eef172f 0x10ecb4000 + 2348847
> 27 org.qt-project.QtQml 0x00010eef0685 0x10ecb4000 + 2344581
> 28 org.qt-project.QtQml 0x00010ee6cd19
> QQmlComponentPrivate::beginCreate(QQmlContextData*) + 889
> 29 org.qt-project.QtQml 0x00010ee6c941
> QQmlComponent::create(QQmlContext*) + 97
> 30 org.qt-project.QtQuick 0x00010eac3ecb
> QQuickView::continueExecute() + 619
> 31 org.qt-project.QtQuick 0x00010eac3c42
> QQuickViewPrivate::execute() + 626
> 32 com.imaginando.ubridge 0x00010db6d22
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Cross-platform alternatives to Apple App Store?

[Vadim Peretokin]

Steam. Blender is in there.

On Mon, 4 Dec 2017, 6:14 am Patrick Stinson,  wrote:

> Hi!
>
> While this may or may not pertain directly to Qt, does anyone have any
> experience with a cross platform alternative to the Apple App Store?
> Hopefully something that plays well with Qt, or at least doesn’t break it?
>
> I am at least looking for in-app subscription purchases for Mac, Windows,
> iOS, Android, Windows mobile.
>
> Apple does take a large cut from Apple store purchases, but I am mostly
> discouraged by the idea of re-releasing an app on different bloody store
> workflows. I figured better to offer a free exe download and then just sell
> subscription tiers in the app.
>
> Thanks,
> -Patrick
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] How to make the QML gui be never stopped on Android

[Vadim Peretokin]

Your users will uninstall your app because of poor battery life if you want
to keep a GUI running while the phone is asleep.

I recommend reconsidering your architecture.

On Thu, 15 Feb 2018, 1:01 pm Denis Shienkov, 
wrote:

> Hi Jérôme,
>
>
> >  android:value="true"/>
>
>
> I already have this property in My manifect file.
>
>
> > That service will need to communicate with your application through
> intent I think. The service could try to wake your application.
>
>
> I need to continue render/update for some dynamic QML GUI even when an
> application goes to sleep.
>
>
> I don't know how to use a service to render a some GUI stuff, e.g. in
> off-screen mode.
>
>
> Maybe I need to use a QTimer which will call the QQuickWindow::update()
> method,
>
> I don't know...
>
>
> Denis.
>
> 15.02.2018 17:37, Jérôme Godbout пишет:
>
> Hi,
>
> I do the following for quick oauth2 background html handling:
>
>  android:value="true"/>
>
> inside the Qt activity tag of the AndroiManifest.xml
>
>
> I wish it was easier to specify a single network activity that can
> continue into the background or at least a network intent that can wake the
> application up (could handle the message an/or bring application up front
> again).
>
>
> I think you will need to create a service to have a full fledge UDP
> listener that continue even after the application screen goes off. That
> service will need to communicate with your application through intent I
> think. The service could try to wake your application. Not a specialist
> about this but this might help, good luck and let us known how you did
> solve it, I'm curious about all this, this still a pain to make those work
> properly.
> --
> *From:* Interest 
>  on behalf of Denis
> Shienkov  
> *Sent:* Thursday, February 15, 2018 9:25:38 AM
> *To:* interest@qt-project.org
> *Subject:* [Interest] How to make the QML gui be never stopped on Android
>
>
> Hi all,
>
> I use QML and Qt 5.9.3 on my Android application.
>
> I achieved some tricks that my application continued to
> work when the smartphone goes to sleep or when the user
> presses the 'power' button, i.e. seems, that an
> application running in background mode.
>
> I do not use an Android service here (because I dont
> know how to do it, also I'm not sure that this will help).
>
> So, when the application goes to background mode,
> I see that it continues to work, because I see that
> my UDP "keep-alive" messages are sends and receives.
>
> But, A MAIN problem is that a QML GUI is stopped then...
> i.e. does not updates.
>
> I need to do GUI grabbing in a real time and send it
> to UDP in any case.
>
> Is it possible to make a GUI work forewer?
> BR,
> Denis
>
>
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] How to programatically make a tab's text bold?

[Vadim Peretokin]

How can I programatically make a tab's text bold? I'm looking to notify the
user that they need to look at it.

Note that this is different from using a stylesheet to set the selected tab
bold - I'd like to set any random tab's text bold.

Been looking at this for several days, appreciate any advice!
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] How to programatically make a tab's text bold?

[Vadim Peretokin]

On Wed, Apr 4, 2018 at 7:35 AM Hamish Moffatt 
wrote:

> On 04/04/18 15:10, Vadim Peretokin wrote:
> > How can I programatically make a tab's text bold? I'm looking to
> > notify the user that they need to look at it.
> >
> > Note that this is different from using a stylesheet to set the
> > selected tab bold - I'd like to set any random tab's text bold.
> >
> > Been looking at this for several days, appreciate any advice!
>
> Using widgets? You didn't say what context.
>
> Maybe you can set a dynamic property on the tab when you want it to be
> bold, and attach a special style using properties in the stylesheet.
>
>
> Hamish
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>

Yes, using widgets.

I've tried a dynamic property however as far as I can see, I can only set
the dynamic property on the entire tab bar - not a specific tab. How can I
set it on a specific tab?
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] How to programatically make a tab's text bold?

[Vadim Peretokin]

Thanks a ton! Works.

On Wed, Apr 4, 2018 at 12:07 PM Igor Mironchik 
wrote:

>
> #include 
> #include 
> #include 
> #include 
> #include 
> #include 
>
> class Style : public QProxyStyle
> {
> public:
> Style( QTabBar * bar )
> :m_boldTab( 0 )
> ,m_bar( bar )
> {
> }
>
> ~Style()
> {
> }
>
> void drawControl( ControlElement element,
> const QStyleOption *option,
> QPainter *painter,
> const QWidget *widget = Q_NULLPTR) const
> {
> if( element == QStyle::CE_TabBarTab )
> {
> if( m_bar->tabAt( option->rect.center() ) == m_boldTab )
> {
> QFont font = widget->font();
> font.setBold( true );
>
> painter->save();
> painter->setFont( font );
> QProxyStyle::drawControl( element, option, painter, widget
> );
> painter->restore();
> }
> else
> QProxyStyle::drawControl( element, option, painter, widget
> );
> }
> else
> QProxyStyle::drawControl( element, option, painter, widget );
> }
>
> private:
> int m_boldTab;
> QTabBar * m_bar;
> };
>
> class Tab : public QTabBar
> {
> public:
> Tab( QWidget * parent )
> :QTabBar( parent )
> ,m_boldTab( 0 )
> {
> }
>
> ~Tab()
> {
> }
>
> protected:
> QSize tabSizeHint(int index) const
> {
> if( index == m_boldTab )
> {
> const QSize s = QTabBar::tabSizeHint( index );
> const QFontMetrics fm( font() );
> const int w = fm.width( tabText( index ) );
>
> QFont f = font();
> f.setBold( true );
> const QFontMetrics bfm( f );
>
> const int bw = bfm.width( tabText( index ) );
>
> return QSize( s.width() - w + bw, s.height() );
> }
> else
> return QTabBar::tabSizeHint( index );
> }
>
> private:
> int m_boldTab;
> };
>
> class TabWidget
> :public QTabWidget
> {
> public:
> TabWidget()
> :m_tabBar( new Tab( this ) )
> ,m_style( m_tabBar )
> {
> m_tabBar->setStyle( &m_style );
> setTabBar( m_tabBar );
> }
>
> ~TabWidget()
> {
> }
>
> private:
> Tab * m_tabBar;
> Style m_style;
> };
>
> int main( int argc, char ** argv )
> {
> QApplication app( argc, argv );
>
> TabWidget t;
> QWidget w1, w2;
> t.addTab( &w1, "Test Tab With Long Name" );
> t.addTab( &w2, "Second Tab" );
>
> t.show();
>
> return app.exec();
> }
>
>
> On 04.04.2018 10:47, Vadim Peretokin wrote:
>
>
> On Wed, Apr 4, 2018 at 7:35 AM Hamish Moffatt 
> wrote:
>
>> On 04/04/18 15:10, Vadim Peretokin wrote:
>> > How can I programatically make a tab's text bold? I'm looking to
>> > notify the user that they need to look at it.
>> >
>> > Note that this is different from using a stylesheet to set the
>> > selected tab bold - I'd like to set any random tab's text bold.
>> >
>> > Been looking at this for several days, appreciate any advice!
>>
>> Using widgets? You didn't say what context.
>>
>> Maybe you can set a dynamic property on the tab when you want it to be
>> bold, and attach a special style using properties in the stylesheet.
>>
>>
>> Hamish
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
>>
>
> Yes, using widgets.
>
> I've tried a dynamic property however as far as I can see, I can only set
> the dynamic property on the entire tab bar - not a specific tab. How can I
> set it on a specific tab?
>
>
> ___
> Interest mailing 
> listInterest@qt-project.orghttp://lists.qt-project.org/mailman/listinfo/interest
>
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Cannot Install 5.2 on Mac OSX Mavericks

[Vadim Peretokin]

Is your Xcode installation fine?
On 14/12/2013 11:18 AM, "Brett (Gmail)"  wrote:

> Hi,
> Has anybody had trouble installing any of the 5.2 released packages on Mac
> OSX 10.9 Mavericks? I can't get any of them to install and given I don't
> see any complaints here, must be something on my side. I tried both
> qt-mac-opensource-5.2.0-clang-offline and
> qt-mac-opensource-5.2.0-ios-x86_64-offline and neither worked.
>
> Messages below.
>
> Any advice appreciated,
> Brett
>
> The error dialog that pops up in the installer says:
>
> Error during installation process (qt.520.clang_64.essentials):
> Command install_name_tool failed.
> Arguments: -change
> /usr/local/Qt-5.2.0/lib/QtGui.framework/Versions/5/QtGui
> /Users/brett/Documents/Development/Qt5.2.0/5.2.0/clang_64/lib/QtGui.framework/Versions/5/QtGui
> -change /usr/local/Qt-5.2.0/lib/QtCore.framework/Versions/5/QtCore
> /Users/brett/Documents/Development/Qt5.2.0/5.2.0/clang_64/lib/QtCore.framework/Versions/5/QtCore
> /Users/brett/Documents/Development/Qt5.2.0/5.2.0/clang_64/plugins/imageformats/libqgif_debug.dylib
> Output:
>
> My system.log is showing messages like this:
>
> Dec 14 08:13:11 Bretts-MacBook-Pro.local sandboxd[1595] ([3781]):
> mdworker(3781) deny file-read-data
> /Users/brett/Documents/Development/Qt5.2.0/5.2.0/clang_64/mkspecs/macx-clang
> (pre-ls-info-2 fstype:hfs fsflag:480D000 flags:24005E diag:0 isXCode:0
> uti:com.apple.application-file
> plugin:/Library/Spotlight/Application.mdimporter - find suspect file using:
> sudo mdutil -t 12201846)
> Dec 14 08:13:11 Bretts-MacBook-Pro.local sandboxd[1595] ([3781]):
> mdworker(3781) deny file-read-data
> /Users/brett/Documents/Development/Qt5.2.0/5.2.0/clang_64/mkspecs/macx-g++-32
> (pre-ls-info-2 fstype:hfs fsflag:480D000 flags:24005E diag:0 isXCode:0
> uti:com.apple.application-file
> plugin:/Library/Spotlight/Application.mdimporter - find suspect file using:
> sudo mdutil -t 12201847)
> Dec 14 08:13:11 Bretts-MacBook-Pro.local sandboxd[1595] ([3781]):
> mdworker(3781) deny file-read-data
> /Users/brett/Documents/Development/Qt5.2.0/5.2.0/clang_64/mkspecs/macx-g++
> (pre-ls-info-2 fstype:hfs fsflag:480D000 flags:24005E diag:0 isXCode:0
> uti:com.apple.application-file
> plugin:/Library/Spotlight/Application.mdimporter - find suspect file using:
> sudo mdutil -t 12201848)
> Dec 14 08:13:11 Bretts-MacBook-Pro kernel[0]: Sandbox: mdworker(3781) deny
> file-read-data
> /Users/brett/Documents/Development/Qt5.2.0/5.2.0/clang_64/mkspecs/macx-g++40
> Dec 14 08:13:11 Bretts-MacBook-Pro.local sandboxd[1595] ([3781]):
> mdworker(3781) deny file-read-data
> /Users/brett/Documents/Development/Qt5.2.0/5.2.0/clang_64/mkspecs/macx-g++
> (pre-ls-info-2 fstype:hfs fsflag:480D000 flags:24005E diag:0 isXCode:0
> uti:com.apple.application-file
> plugin:/Library/Spotlight/Application.mdimporter - find suspect file using:
> sudo mdutil -t 12201848)
> Dec 14 08:13:11 Bretts-MacBook-Pro kernel[0]: Sandbox: mdworker(3781) deny
> file-read-data
> /Users/brett/Documents/Development/Qt5.2.0/5.2.0/clang_64/mkspecs/macx-g++42
> Dec 14 08:13:11 Bretts-MacBook-Pro kernel[0]: Sandbox: mdworker(3781) deny
> file-read-data
> /Users/brett/Documents/Development/Qt5.2.0/5.2.0/clang_64/mkspecs/macx-icc
> Dec 14 08:13:11 Bretts-MacBook-Pro kernel[0]: Sandbox: mdworker(3781) deny
> file-read-data
> /Users/brett/Documents/Development/Qt5.2.0/5.2.0/clang_64/mkspecs/macx-ios-clang
> Dec 14 08:13:11 Bretts-MacBook-Pro kernel[0]: Sandbox: mdworker(3781) deny
> file-read-data
> /Users/brett/Documents/Development/Qt5.2.0/5.2.0/clang_64/mkspecs/macx-llvm
> Dec 14 08:13:16 Bretts-MacBook-Pro.local mdworker[3781]: (Normal) Import:
> Using too many resources after 1536 files (wired: 0 resident: 5356 swapped:
> 0 regions: 2080), hit usage threshold importing
> /Users/brett/Documents/Development/Qt5.2.0/5.2.0/clang_64/examples/widgets/tools/i18n/translations/i18n_fr.ts,
> exiting to clean up now.
> Dec 14 08:13:16 Bretts-MacBook-Pro.local mdworker[3780]: (Normal) Import:
> Using too many resources after 1536 files (wired: 0 resident: 4123 swapped:
> 0 regions: 2079), hit usage threshold importing
> /Users/brett/Documents/Development/Qt5.2.0/5.2.0/clang_64/examples/widgets/widgets/stylesheet/layouts/default.ui,
> exiting to clean up now.
> Dec 14 08:13:17 Bretts-MacBook-Pro.local mdworker[3782]: (Normal) Import:
> Using too many resources after 1536 files (wired: 0 resident: 4174 swapped:
> 0 regions: 2073), hit usage threshold importing
> /Users/brett/Documents/Development/Qt5.2.0/5.2.0/clang_64/doc/qtsql/scripts,
> exiting to clean up now.
> Dec 14 08:13:17 Bretts-MacBook-Pro.local mdworker[3779]: (Normal) Import:
> Using too many resources after 1536 files (wired: 0 resident: 4149 swapped:
> 0 regions: 2080), hit usage threshold importing
> /Users/brett/Documents/Development/Qt5.2.0/5.2.0/clang_64/doc/activeqt/images/used-in-examples,
> exiting to clean up now.
>
>
> ___
> Interest ma

Re: [Interest] Poor mirror performance for the online Qt SDK

[Vadim Peretokin]

You aren't the only one. I get the same Chinese mirror in Australia and it
is terrible. It taught me that wget has a default retry limit of 20 times!

The online installer and the browser download are not useable in Australia,
even on a fibre connection. Download the offline installer and either use
wget with infinite retries (it'll keep picking up where it left from,
thankfully), or click on the "info" link on the Qt website to download from
a different mirror, or use aria2c  which can
download from many mirrors at once and will download it in a reasonable
time.

I've already written to the Contact form on the Qt project on the website
about this, but I have not had any reply yet.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] device not open from Qt

[Vadim Peretokin]

Using Qt 5.2, I'm getting the following warning: "QIODevice::read: device
not open" when invoking QDialog::exec(). How can I go about fixing this? It
seems to be coming from Qt and is new after the upgrade to Qt5.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] device not open from Qt

[Vadim Peretokin]

Works, thanks!
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt5 and (lack of!) font rendering quality (Linux/X11)

[Vadim Peretokin]

It's not a bug, it's a feature! That is what I was told. Apparently Qt4 was
getting the font boldness wrong and they fixed it in Qt5. Not sure if user
experience was ever factored into the decision.

Search Google for "Qt5 font rendering", you will find that lots of other
people have already ran into this.

On Tue, Oct 21, 2014 at 5:36 AM, René J.V.  wrote:

> I posted this on the Qt forums earlier, but it was suggested to repost
> here:
>
> I’m a bit of a font freak, so I have “bohoomil”‘s Ultimate version of the
> Infinality patches to libfreetype6 and fontconfig installed. It does
> wonders to my KDE4-based desktop, giving text a quality that’s just about
> as good as with MS Window’s ClearType (using Segoe UI semi-bold as my
> desktop font) and better than OS X’s font rendering.
>
> Recently I have been playing a bit with “Project Neon5”, (K)Ubuntu’s KDE
> Frameworks 5 playground, to get a preview of what’s supposed to become the
> next KDE desktop. It’s built atop Qt 5.3.2 .
>
> Font rendering is horrible when starting KF5 applications from under a
> KDE4 session: blocky and something is clearly off with RGB antialiasing.
> Thinking it might be due to running beta-quality software in a “subsession”
> rather than a standalone session, I thought I’d had a look at “pure” Qt5
> from the official (K)Ubuntu repos. That’s Qt 5.2.1 to be exact.
>
> Font rendering is better here, but it’s still a far cry from being as nice
> as under Qt4. Part of that is due to Qt5 not respecting my choice of fonts
> (picking an unknown other font) but it also seems there’s no distinction
> being made between medium (semi-bold) and bold, making everything look
> either too heavy or too light. I already have to work around this “feature”
> to treat semi-bold fonts as regular bold in Qt on OS X (Qt4 and Qt5 are
> handicapped alike there in this aspect), I REALLY hope that Qt5 on Linux
> won’t follow suit …!
>
> Infinality Ultimate's author bohoomil had this to say on the subject (
> https://plus.google.com/u/0/+bohoomil-infinality-bundle/posts/SL2jrL9VJyt?cfem=1
> ):
> "Qt5 is, well, a bit of a mystery to me, too. As far as I can tell, the
> font rendering issues are common regardless of whether you use stock
> freetype2 or the patched one: Qt5 apps just stand out which makes me think
> that the toolkit must be much too different internally from its
> predecessor. (It has been already reported on fontconfig-ultimate bug
> tracker.) By the way, it reminds me of Chrome's approach which also, 'by
> design', doesn't play nicely with Linux's font rendering backend
> (fontconfig in this case: one of the things that won't work is font
> substitution). I think we just have to wait and see how Qt5 advances as
> it's still under heavy development."
>
> Thoughts, reactions or other feedback welcome!
>
> René
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt5 and (lack of!) font rendering quality (Linux/X11)

[Vadim Peretokin]

That seems to be unrelated to the font boldness issue I see in Qt5. Just
another artefact of the font rewrite in Qt5 introducing issues.

On Tue, Oct 21, 2014 at 6:45 AM, Mark Gaiser  wrote:

> On Mon, Oct 20, 2014 at 10:11 PM, René J.V.  wrote:
> > On Tuesday October 21 2014 05:45:51 Vadim Peretokin wrote:
> >
> >> It's not a bug, it's a feature! That is what I was told. Apparently Qt4
> was
> >> getting the font boldness wrong and they fixed it in Qt5. Not sure if
> user
> >
> > Yes, it does. Under OS X. Not under Linux, where Qt4 gives me perfect
> light, regular, semi-bold and bold. With Infinality Ultimate installed, of
> course ;)
> >
> >> experience was ever factored into the decision.
> >
> > Eh? There's a contradictio in terminis there. Font rendering quality is
> all user experience, so either you fix it (and quality issues disappear) or
> you break it completely (and quality disappears) ...
> >
> >>
> >> Search Google for "Qt5 font rendering", you will find that lots of other
> >> people have already ran into this.
> >
> > With Digia trying to convince them that they're wrong and just have to
> live with fugly fonts as X11's first attempts at using TrueType fonts (i..e
> way worse that handcrafted bitmap fonts)?
>
> I didn't really look into this, but "something" seems to be fixed in
> the font rendering department for Qt 5.4.0:
> https://bugreports.qt-project.org/browse/QTBUG-27106
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Accessibility: how to notify of new text in an unfocused widget?

[Vadim Peretokin via Interest]

Hi all,

I'm working on adding accessibility support for my Qt 5.15 application
and I need the screenreader to announce when a widget that is outside of
the screenreaders focus receives new text.

In the web world, this is solved with live regions
. I'm not able to find
them in Qt's documentation and JIRA suggests that they are not supported
. 

How can I go about solving this in my application? Also interested to
hear from those who ran up against this and how you solved this.

Ideally this could be dealt with application-side without modifying Qt,
as maintaining builds of Qt sources would be a large amount of overhead
for our open-source project.

Thanks,
Vadim
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Official linuxdeployqt ?

[Vadim Peretokin via Interest]

Just to correct some biases here, in my opinion as a software publisher
AppImage is still the simplest way for a user to run your app. 

To get Mudlet (a FOSS text games client) all you need to do is go to
https://www.mudlet.org/download, download the .tar, right-click to
extract it and double-click to run. 

It really is that simple; experienced and unexperienced users alike
across many different Linux distributions make it work.

Try to replicate that with snap or flatpak - you won't be able to
without messing in the terminal or relying on distro-specific
distribution channels. Nothing beats AppImage for a truly distro
agnostic image distribution format, and I'm speaking from having used it
for years to distribute my software.

BR

On August 8, 2022, Vadim Peretokin via Interest  wrote:
> On 8/8/22 16:09, Jörg Bornemann wrote:
> > Mitch already pointed you to QTBUG-74940.  The biggest question 
> > regarding a linuxdeployqt is: what exactly is the deployment format 
> > going to be?  There's no standard way of deploying Linux
> applications. 
> > There are many.
> >
> > The community contributions create AppImage packages.  That seems
> to 
> > be a reasonable choice.  Other opinions?
>
>
> Like Roland said, it has to be Flatpak. I haven't seen anyone talking 
> about AppImage in years, and Snap is too Ubuntu-specific.
>
>
> windeployqt doesn't package anything though, so should linuxdeployqt? 
> macdeployqt only sort of does, with its dmg support.
>
>
> Hamish
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest