Re: [Interest] Customized Qt Platform Abstraction plugin

2017-11-17 Thread Philippe
> You can do hybrid apps in Qt, I did one in MFC and Qt. Remember at some level > Qt is "just a library". I'd imagine that at some point though you'd need to > merge the event loops depending on the level of intertop required. If you > don't have the same process/address space you'll need some

Re: [Interest] Customized Qt Platform Abstraction plugin

2017-11-17 Thread Jason H
> Sent: Friday, November 17, 2017 at 12:02 PM > From: Philippe > To: interest@qt-project.org > Subject: [Interest] Customized Qt Platform Abstraction plugin > > There is little documentation about Qpa, however I am wondering if a custom > Qpa plugin could be used for the followin scenario: > >

[Interest] Customized Qt Platform Abstraction plugin

2017-11-17 Thread Philippe
There is little documentation about Qpa, however I am wondering if a custom Qpa plugin could be used for the followin scenario: * there is a big desktop application A that does not use Qt, and that uses its own xplatform framework. * there is smaller application B, that is based on Qt widgets *

Re: [Interest] Performance comparison of painting methods

2017-11-17 Thread Allan Sandfeld Jensen
On 13.11.2017 17:12, Jean-Michaël Celerier wrote: http://kgronholm.blogspot.fr/2017/11/qt-510-qml-shape-testing.html An interesting blog post which compares QPainter, the upcoming QML Shapes and QNanoPainter. I'm surprised to see QML Shapes perform so much slower than good old QPainter. Do

Re: [Interest] Two QCoreApplication objects with a twist

2017-11-17 Thread Thiago Macieira
On sexta-feira, 17 de novembro de 2017 08:22:42 PST Konstantin Tokarev wrote: > > Signals and slots do not require QCoreApplication. > > But queued connections do (or is standalone QEventLoop enough?) They need an event dispatcher. See below about event loop integration. That said, we always say

Re: [Interest] Two QCoreApplication objects with a twist

2017-11-17 Thread Konstantin Tokarev
17.11.2017, 19:11, "Thiago Macieira" : > On sexta-feira, 17 de novembro de 2017 00:17:29 PST Lorenz Haas wrote: >>  you can't use two QCoreApplication instances in a single application, >>  I know. There's also a nice warning: >>  https://github.com/qt/qtbase/blob/5.10/src/corelib/kernel/qcoreapp

Re: [Interest] Two QCoreApplication objects with a twist

2017-11-17 Thread Thiago Macieira
On sexta-feira, 17 de novembro de 2017 00:17:29 PST Lorenz Haas wrote: > you can't use two QCoreApplication instances in a single application, > I know. There's also a nice warning: > https://github.com/qt/qtbase/blob/5.10/src/corelib/kernel/qcoreapplication.c > pp#L795. The reason, I guess, has to

Re: [Interest] Two QCoreApplication objects with a twist

2017-11-17 Thread Jean-Michaël Celerier
Wouldn't it be simpler to recompile the shared library with a namespaced version of Qt ? (eg build Qt from source and pass "-namespace myqt" to the script IIRC ; this puts every Qt class in a namespace, hence they would appear as different functions & statics). --- Jean-Michaël Celerier htt

[Interest] Two QCoreApplication objects with a twist

2017-11-17 Thread Lorenz Haas
Hi, you can't use two QCoreApplication instances in a single application, I know. There's also a nice warning: https://github.com/qt/qtbase/blob/5.10/src/corelib/kernel/qcoreapplication.cpp#L795. The reason, I guess, has to do with the static variables used in QCA (?). Now, however, please imagin