We're currently using Qt 5.6 but looking to upgrade soon. I tried building our
app on Qt 5.11.1 with Visual Studio 2017 V15.8.2 and it failed on the first
file:
1>c:\qt\qt5.11.1\5.11.1\msvc2015\include\qtcore\qalgorithms.h(51): error C4430:
missing type specifier - int assumed. Note: C++ does
On Wednesday, 5 September 2018 12:57:39 PDT Uwe Rathmann wrote:
> On Wed, 05 Sep 2018 09:55:41 -0700, Thiago Macieira wrote:
> >> It also raises questions about the status of the X11 paint engine.
> >> Several bugs have been closed because of not fixing the X11 paint
> >> engine anymore.
> >
> >
On Tuesday, 4 September 2018 23:26:27 PDT André Pönitz wrote:
> > Because it's not an important improvement for most people. Your case and
> > Denis's, as seen in this thread, are very specific. Most people are
> > fine with the raster engine.
>
> If "Most people do not $X" were a sensible line
On Wed, 05 Sep 2018 09:55:41 -0700, Thiago Macieira wrote:
>> It also raises questions about the status of the X11 paint engine.
>> Several bugs have been closed because of not fixing the X11 paint
>> engine anymore.
>
> This being the reason why the X11 engine is not good for everyone.
O.k. -
On Wed, 05 Sep 2018 13:04:39 +0300, Denis Shienkov wrote:
> Uwe, wow :) What Qt5 version are you use?
Seems to work with Qt5 >= 5.10.
Uwe
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On Wed, Sep 05, 2018 at 09:55:41AM -0700, Thiago Macieira wrote:
> On Wednesday, 5 September 2018 02:29:15 PDT Uwe Rathmann wrote:
> > I also googled for QT_XCB_NATIVE_PAINTING without almost no results. I
> > understand, that reverting a decision is not stuff for big announcements,
> > but for
On Wednesday, 5 September 2018 09:57:30 PDT Thiago Macieira wrote:
> On Wednesday, 5 September 2018 00:20:22 PDT Helio Chissini de Castro wrote:
> > jsonplugin2.moc:153:1: error: narrowing conversion of ‘'\303'’
> > from ‘char’ to ‘unsigned char’ inside { } [-Wnarrowing]
> > };
>
> [cut]
On Wednesday, 5 September 2018 00:20:22 PDT Helio Chissini de Castro wrote:
> jsonplugin2.moc:153:1: error: narrowing conversion of ‘'\303'’
> from ‘char’ to ‘unsigned char’ inside { } [-Wnarrowing]
> };
[cut]
> lude/jsonplugin2.moc:123:48: error: constant expression evaluates to -61
>
On Wednesday, 5 September 2018 02:29:15 PDT Uwe Rathmann wrote:
> I also googled for QT_XCB_NATIVE_PAINTING without almost no results. I
> understand, that reverting a decision is not stuff for big announcements,
> but for such an important improvement: has it been communicated at least
>
On 9/5/18 2:11 PM, Ville Voutilainen wrote:
On 5 September 2018 at 14:42, Helio Chissini de Castro wrote:
Unfortunately not.
Just compiled again reverting this commit and the issue still there.
No ideas for now :-/
Any volunteers to bisect the problem?
Most likely
On 5 September 2018 at 14:42, Helio Chissini de Castro wrote:
> Unfortunately not.
>
> Just compiled again reverting this commit and the issue still there.
>
> No ideas for now :-/
Any volunteers to bisect the problem?
___
Development mailing list
Unfortunately not.
Just compiled again reverting this commit and the issue still there.
No ideas for now :-/
On Wed, 5 Sep 2018 at 10:17, Liang Qi wrote:
> Perhaps it's related with https://codereview.qt-project.org/#/c/235352/ .
>
> --Liang
>
> On Wed, 5 Sep 2018 at 09:20, Helio Chissini de
Am 05.09.2018 um 12:40 schrieb Peter Hartmann:
> Hello Robert,
>
> On 04.09.2018 14:03, Robert Löhning wrote:
>> I saw your post and it helped me get started. Thanks for that!
>
> cool, thanks for the feedback!
>
>>
>> By the way: In step 1 you use
>> -fsanitize-coverage=edge
>> whereas I
Hi,
You may have noticed that CI is having problems to get build machines and
builds seems to be in stuck. This is because machines aren't booting up at all
or the booting time is very slow.
CI team is investigating the problem
Br
Heikki Halmet
Hello Robert,
On 04.09.2018 14:03, Robert Löhning wrote:
> I saw your post and it helped me get started. Thanks for that!
cool, thanks for the feedback!
>
> By the way: In step 1 you use
> -fsanitize-coverage=edge
> whereas I followed LLVM's example [1] and used
>
> Using Qwt with a current Qt version seems to run
the same ways as with Qt4/X11 without any problems.
Uwe, wow :) What Qt5 version are you use?
Denis
ср, 5 сент. 2018 г. в 12:31, Uwe Rathmann :
> On Wed, 05 Sep 2018 09:56:36 +0100, Sérgio Martins via Development wrote:
>
> >> What needs to be
On Wed, 05 Sep 2018 09:56:36 +0100, Sérgio Martins via Development wrote:
>> What needs to be done to make it become effective ?
>
> export QT_XCB_NATIVE_PAINTING=1
I did a quick check with using QPainter on a QPixmap and indeed it runs
the X11 paint engine. Using Qwt with a current Qt version
Integrations
* qt5 5.11/5.11.2/5.12 integrations are healthy, finally for 5.12
* qt5 dev, 5.12->dev merge + dev submodule update integration just started,
let's see
COIN is a bit slow recently, the difference between backend vm numbers and coin
running numbers is a bit too much. Colleagues
On 2018-09-05 06:58, Uwe Rathmann wrote:
On Tue, 04 Sep 2018 20:51:38 +0200, Martin Koller wrote:
added the native X11 graphicssystem support from Qt4 to Qt5
Very cool.
Andrew told me that there were 2 concurrent attempts to revive X11 as
the
situation for running widget applications on
Hi,
> added the native X11 graphicssystem support from Qt4 to Qt5
According to that commit (and next depends commits), seems this porting is
not completed yet to Qt5.
So, it is interest to know: can we use it in current time, and since what
of Qt version? Is it work at all as in Qt4?
And, as
Perhaps it's related with https://codereview.qt-project.org/#/c/235352/ .
--Liang
On Wed, 5 Sep 2018 at 09:20, Helio Chissini de Castro wrote:
> Morning guys
>
> After compile 5.12 branch from yesterday morning, i got one KDE
> application failing due a compiler error on a generated moc file.
Morning guys
After compile 5.12 branch from yesterday morning, i got one KDE application
failing due a compiler error on a generated moc file.
Is there any moc relevant change ? I didn't change my compiler environment
from previous 5.11 and always compile all in a clean chroot, with no
previous
On Tue, 04 Sep 2018 20:51:38 +0200, Martin Koller wrote:
> added the native X11 graphicssystem support from Qt4 to Qt5
Very cool.
Andrew told me that there were 2 concurrent attempts to revive X11 as the
situation for running widget applications on remote desktops is simply
not good, when
23 matches
Mail list logo
