On Tuesday, 5 December 2017 13:36:09 PST René J.V. Bertin wrote:
> On Tuesday December 05 2017 11:11:12 Thiago Macieira wrote:
> > Ok, the only differences between 5.9 and 5.10 are replacing 0 with nullptr
> > and removing one no-op.
>
> Has anything changed in the handling of style plugins
On Tuesday December 05 2017 11:11:12 Thiago Macieira wrote:
> Ok, the only differences between 5.9 and 5.10 are replacing 0 with nullptr
> and
> removing one no-op.
Has anything changed in the handling of style plugins between 5.8 and 5.9?
A few more lines of output later I now know that the
On Tuesday, 5 December 2017 10:42:54 PST René J. V. Bertin wrote:
> Thiago Macieira wrote:
> > Please upgrade to 5.10 and apply the fixes again. But other than that,
> > there are no known issues because there aren't many changes either.
>
> I don't think I'll be trying 5.10 any time soon, 5.9 is
Thiago Macieira wrote:
> Please upgrade to 5.10 and apply the fixes again. But other than that, there
> are no known issues because there aren't many changes either.
I don't think I'll be trying 5.10 any time soon, 5.9 is the newest version I
hope I'll be able to run across all my systems.
R.
On Tuesday, 5 December 2017 08:23:05 PST René J. V. Bertin wrote:
> Thiago Macieira wrote:
> > Keep applying the patch on top of the official release.
>
> Wasn't that clear? I'm still running 5.8 *with* the fixes.
No, it wasn't.
Please upgrade to 5.10 and apply the fixes again. But other than
René J. V. Bertin wrote:
> It appears to be an issue caused by (with?) the QtCurve widget style, though.
One that goes away when I add an output tracer just before exiting from the
style's dtor ... =/
R
___
Development mailing list
Thiago Macieira wrote:
> Keep applying the patch on top of the official release.
Wasn't that clear? I'm still running 5.8 *with* the fixes.
This does look like a related-but-different issue though, trying to disconnect
a
valid receiver from a sender instance which has apparently already been
On Tuesday, 5 December 2017 06:34:26 PST René J.V. Bertin wrote:
> Is the crash below another (new?) variant of the on-exit QDBus crashes for
> which a few fixes were pushed a couple months ago, a new bug I should
> report, or is this the result of a bug in the dependent code?
The fixes were
Hi,
Is the crash below another (new?) variant of the on-exit QDBus crashes for
which a few fixes were pushed a couple months ago, a new bug I should report,
or is this the result of a bug in the dependent code?
rekonq built on Linux from the frameworks git head, Qt 5.8 (with the QDBus
patches
On 2017-12-04 21:05, Ville Voutilainen wrote:
Same goes for semantics.
In fact, I'm _mainly_ concerned with semantics. Different method naming
is trivially fixed by tooling these days, as long as the semantics are
the same.
As a trivial example: qAsConst, like std::as_const, has the rvalue
10 matches
Mail list logo
