DirectFB.org is down and has been down since at August 1, 2015. The last
commit on the GitHub mirror is actually from 2014. Our last non-buildsystem
change there prior to my compile fix is from September 2015.
I'd like to turn off the automatic detection in the Unix configure for Qt 5.6.
This w
On terça-feira, 15 de março de 2016 10:26:15 PDT Thiago Macieira wrote:
> Unfortunately, there's something wrong with the new threaded solution. I'm
> still investigating whether there's only one bug or if there are two. The
> semaphore that was hit should never have been hit, but it's only getti
Hi,
Did you file a bug report? ML is not really the right place for reporting
bugs.
Briefly, the CJK characters in your text are covered by some fallback font
for which the font metrics are slightly different, so that the line height
is the sum of a max ascent, max descent, and max leading (see
Q
2016-03-14 21:36 GMT+02:00 Jan Kundrát :
>> That's kded/kiod, not Plasma.
>
>
> Yes; however, given that kded is used in a default configuration of Plasma
> 5, the end result is that the Plasma panel (and krunner, and possibly other
> components) "won't work" with the current version of Qt 5.6.
Ju
On terça-feira, 15 de março de 2016 08:14:16 PDT Thiago Macieira wrote:
> Again: when it was reported, it sounded like a race condition that was hit
> only infrequently, if you were unlucky. Only when Jan reported in this
> thread that it is happening all the time did it sound more serious.
I've
On Tuesday 15 March 2016 15:43:09 Poenitz Andre wrote:
> > It's not impossible that this could be
> > exploited, too, e.g. if the app divides by a non-isNull rect's width and
> > the attacker forges the coordinates such that width() return 0
>
> Please describe how that can happen.
Run tst_qrect
Hello everybody!!!
I have been testing Qt5.6
of course Beta an RC releases have some bugs as expected.
But in all recent linux releases including the final 5.6.0 release the QML
design view is completely unusable.
Even the most simple qml led to "Qt Quick emulation layer crashed (1:0)"
I have
On terça-feira, 15 de março de 2016 09:54:46 PDT Helio Chissini de Castro
wrote:
> 5.6.0 is more important than regular releases, as Qt project defined as the
> LTS release, and this bug do Qt LTS been unusable for the largest showcase
> of Qt which is really a not good presentation.
5.6 is the L
On terça-feira, 15 de março de 2016 07:51:09 PDT Knoll Lars wrote:
> I understand that this is an issue for KDE, but since it only happens when
> using qDBusAddSpyHook I am convinced it’ll hit almost no other user. So
> while KDE is important, I don’t think this is a good enough reason to block
> t
That’s unfortunate, but the fix for this one will have to wait for 5.6.1 as
well.
Cheers,
Lars
On 15/03/16 15:35, "Releasing on behalf of Hernan Martinez via Releasing"
wrote:
>Hello.
>
>Thank you for announcing the final packages.
>
>There’s still a P1 Critical Bug affecting Qt Quick its
Marc Mutz wrote:
> > Cluttering up the API doesn’t seem nice. Also not sure what you mean by
> > new users needing such large rectangles… if they do, why don’t they use
> > QRectF?
>
> For one, QRectF has different semantics w.r.t. wdith()/height(), for another,
> sizeof(QRectF) == 2 * sizeof(Q
On Tuesday 15 March 2016 14:44:12 Rutledge Shawn wrote:
> > On 15 Mar 2016, at 15:43, Marc Mutz wrote:
> >
> > On Tuesday 15 March 2016 13:08:42 Bo Thorsen wrote:
> >> Den 15-03-2016 kl. 14:07 skrev Marc Mutz:
> > [...]
> >
> >> There is another option that doesn't mean a change of signature: Bo
On Tuesday 15 March 2016 14:48:52 Иван Комиссаров wrote:
> We can also validate rect on construction and allow to create rects no
> bigger than QRect(*, *, MAX_INT, MAX_INT) rects?
No. The ctors are constexpr nothrow now. We must maintain the wide contract.
In Qt 6, I'd normalise on construction,
We can also validate rect on construction and allow to create rects no
bigger than QRect(*, *, MAX_INT, MAX_INT) rects?
2016-03-15 16:44 GMT+03:00 Poenitz Andre :
>
> On Tuesday 15 March 2016 13:08:42 Bo Thorsen wrote:
> > > Den 15-03-2016 kl. 14:07 skrev Marc Mutz:
> > [...]
> > > There is anoth
On Tuesday 15 March 2016 13:08:42 Bo Thorsen wrote:
> > Den 15-03-2016 kl. 14:07 skrev Marc Mutz:
> [...]
> > There is another option that doesn't mean a change of signature: Bound
> > the result. So if the real result is > INT_MAX, return INT_MAX. Same for
> > INT_MIN.
> >
> > Yes, it's not the c
> On 15 Mar 2016, at 15:43, Marc Mutz wrote:
>
> On Tuesday 15 March 2016 13:08:42 Bo Thorsen wrote:
>> Den 15-03-2016 kl. 14:07 skrev Marc Mutz:
> [...]
>> There is another option that doesn't mean a change of signature: Bound
>> the result. So if the real result is > INT_MAX, return INT_MAX. S
Hi everyone,
I have been fighting with this bug for over a year, but till now I can't find a
satisfying solution, so I came here.
I use QPlainTextEdit to implement my own code editor widget, much like the
tutorial does. The widget works fine, except it displays CJK characters with a
differe
On Tuesday 15 March 2016 13:08:42 Bo Thorsen wrote:
> Den 15-03-2016 kl. 14:07 skrev Marc Mutz:
[...]
> There is another option that doesn't mean a change of signature: Bound
> the result. So if the real result is > INT_MAX, return INT_MAX. Same for
> INT_MIN.
>
> Yes, it's not the correct result,
Hi,
There is already a code review article:
https://codereview.qt-project.org/#/c/152345/
I have also created the bug reference:
https://bugreports.qt.io/browse/QTBUG-51879
If I compile with "configure -skip qt3d", then everything compiles. That tells
me that only this issue is the actual sho
Den 15-03-2016 kl. 14:07 skrev Marc Mutz:
Hi,
No, this is not about the +1.
QRect is internally represented as QPoint topLeft, bottomRight, which means it
can hold rectangles for which width() and height(), returning ints, may
overflow, e.g.
QRect{{INT_MIN, INT_MIN}, QPoint{0, 0}}
QRec
Hi,
No, this is not about the +1.
QRect is internally represented as QPoint topLeft, bottomRight, which means it
can hold rectangles for which width() and height(), returning ints, may
overflow, e.g.
QRect{{INT_MIN, INT_MIN}, QPoint{0, 0}}
QRect{{INT_MIN, INT_MIN}, QPoint{INT_MAX, INT_MA
11:42, 15 марта 2016 г., Heikkinen Jani :Hi!Release isn't done yet and so on there isn't tag either yet. It should be there when release is officially doneBr,Jani-Original Message-From: Development [mailto:development-bounces+jani.heikkinen=theqtcompany@qt-project.org] On Behalf OfKonst
Is there a bug report about this issue? if no please create one in
https://bugreports.qt.io/secure/Dashboard.jspa
I won't block release because of this any more, let's see if we can fix this
for 5.6.1; Qt3D is still TP and it is compiling OK in most cases.
Btw, please add as much info as poss
Hi,
On Tuesday 15 Mar 2016 09:19:12 Walter Stefan wrote:
> Hi,
>
> I am still facing an issue with the mentioned source package on CentOS 6.x
> with the g++ 4.4.7 in Qt3D. I don't know if that will be solved from your
> end and I don't know if that would delay the release.
>
> For me it is very
On 15/03/16 09:54, "Development on behalf of Helio Chissini de Castro"
wrote:
>I agreed partially with Lars
>
>
>Is too late *now*, and we can wait for a quick 5.6.1, but is not entirely
>correct in say that we're not raising this issue from some time.
>For us in Fedora this issue been happeni
Hi,
I am still facing an issue with the mentioned source package on CentOS 6.x with
the g++ 4.4.7 in Qt3D. I don't know if that will be solved from your end and I
don't know if that would delay the release.
For me it is very important because Qt 5.6.0 will be a LTE release and CentOS
6.x is no
I agreed partially with Lars
Is too late *now*, and we can wait for a quick 5.6.1, but is not entirely
correct in say that we're not raising this issue from some time.
For us in Fedora this issue been happening for a month, since rc releases
and the bug was opened 10 days ago so the fact that is p
Hi!
Release isn't done yet and so on there isn't tag either yet. It should be there
when release is officially done
Br,
Jani
>>-Original Message-
>>From: Development [mailto:development-
>>bounces+jani.heikkinen=theqtcompany@qt-project.org] On Behalf Of
>>Konstantin Podsvirov
>>Sent
Hi,
The report was marked as a P2, and nobody raised it to be a showstopper for the
release. Trying to do this on the day before is unfair to everybody else.
I understand that this is an issue for KDE, but since it only happens when
using qDBusAddSpyHook I am convinced it’ll hit almost no other
29 matches
Mail list logo
