Kevin Funk wrote:
> The latter, yes. Just try.
Took me a while because I was upgrading to Qt 5.6.0.
Running
%> QT_LOGGING_RULES="*=true;qt.scenegraph*.debug=false" kdevelop5
Here's what I get when opening a 1st document over the welcome page:
kdevplatform.sublime: view added in Sublime::Area(0
René J.V. Bertin wrote:
Hi again,
> mOptions.testFlag(UseFreeTypeFontEngine)? 1.0 : 2.0
In fact, 0.95 may work even better than 1.0 .
R.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On Tuesday 22 March 2016 12:03:40 Marc Mutz wrote:
> On Tuesday 22 March 2016 11:20:44 Thiago Macieira wrote:
> > On terça-feira, 22 de março de 2016 07:17:53 GMT Marc Mutz wrote:
> > > This is a general issue in C++ and should be solved generally:
> > >
> > > http://www.open-std.org/jtc1/sc22/wg2
In the docs I find:
"If there is a QLayout that manages this widget's children, the size policy
specified by that layout is used. If there is no such QLayout, the result of
this function is used."
However in the code I can not find a relation between the sizePolicy and a
layout.
QWidget::sizePo
On terça-feira, 22 de março de 2016 11:12:52 GMT Blasche Alexander wrote:
> The problem seem purely license related (other failures currently not
> visible). I would argue that we should fix integrations errors due to such
> issues.
>
> I would favor another option though. We should disable the li
The problem seem purely license related (other failures currently not visible).
I would argue that we should fix integrations errors due to such issues.
I would favor another option though. We should disable the license check for
modules which are ignored by .gitmodules.
--
Alex
_
On terça-feira, 22 de março de 2016 12:00:35 GMT Marc Mutz wrote:
> The same old problem:
>
> std::_1::initializer_list vs. std:.initializer_list ? Or is
> std::initializer_list one of those types (like std::exception) compatible
> between libc++ and libstdc++?
Good question. The layout of std:
On Tuesday 22 March 2016 11:20:44 Thiago Macieira wrote:
> On terça-feira, 22 de março de 2016 07:17:53 GMT Marc Mutz wrote:
> > This is a general issue in C++ and should be solved generally:
> >
> > http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4035.pdf
>
> Do you know the status of t
On Tuesday 22 March 2016 11:33:57 Thiago Macieira wrote:
> [This is why I asked for an analysis of the features now possible, but it
> hasn't happened. So we're doing it piecemeal]
>
> Sean wrote:
> > I don't have ready access to all the other compilers and versions we
> > support but I think this
[This is why I asked for an analysis of the features now possible, but it
hasn't happened. So we're doing it piecemeal]
Sean wrote:
> I don't have ready access to all the other compilers and versions we support
> but I think this would allow potential use of:
>
> * template aliases
> * raw strin
On terça-feira, 22 de março de 2016 07:17:53 GMT Marc Mutz wrote:
> This is a general issue in C++ and should be solved generally:
>
> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4035.pdf
Do you know the status of this proposal? It's not in the latest language draft
available (N4567
On Tue, Mar 22, 2016, at 10:37 AM, Hausmann Simon wrote:
> I'm not sure what you'd like me to answer at this point. I think that it
> is possible to fix the
> build of these modules, the CI system is in place for that. However it
> requires a fair bit of
> work (ask Robin about qtmessagingframework
I'm not sure what you'd like me to answer at this point. I think that it is
possible to fix the
build of these modules, the CI system is in place for that. However it requires
a fair bit of
work (ask Robin about qtmessagingframework ;-).
However fixing the modules appears to me to be orthogonal
On Tuesday 22 March 2016 09:58:48 Hausmann Simon wrote:
> As the modules are not part of any release of Qt and unmaintained, I don't
> think they need fixing.
C'mon — FTBFS without the possibility to submit a fix?
--
Marc Mutz | Senior Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB G
As the modules are not part of any release of Qt and unmaintained, I don't
think they need fixing.
Simon
From: m...@kdab.com on behalf of Marc Mutz
Sent: Tuesday, March 22, 2016 9:37
To: Hausmann Simon
Cc: development@qt-project.org
Subject: Re: [Devel
On Tuesday 22 March 2016 09:19:26 Hausmann Simon wrote:
> Hi,
>
> I see no reason for dropping them from qt5.git as long as they are in
> status = ignore
> (http://code.qt.io/cgit/qt/qt5.git/tree/.gitmodules?h=5.6.0 ). What harm
> does it cause?
You mean other than failing integrations? None.
Sp
Hi,
I see no reason for dropping them from qt5.git as long as they are in status =
ignore (http://code.qt.io/cgit/qt/qt5.git/tree/.gitmodules?h=5.6.0 ). What harm
does it cause?
Simon
From: Development
on behalf
of Marc Mutz
Sent: Tuesday, March 22,
Hi,
what, exactly, is the status of the QtFeedback and QtDocGallery modules? They
are submodules of qt5/5.6, but they accept no integrations due to the license
header check failing, cf.
https://codereview.qt-project.org/151189 (qtfeedback)
https://codereview.qt-project.org/151253 (qtdocga
Not implemented feature. That site is a mirror of the internal system and we do
not mirror running integrations currently.
Simon
Original Message
From: Marc Mutz
Sent: Tuesday, March 22, 2016 08:50
To: development@qt-project.org
Subject: Re: [Development] http://testresults.qt.io/ci/status/ s
On Tuesday 22 March 2016 07:32:45 Liang Qi wrote:
> The status of new CI: http://testresults.qt.io/coin/
About that: it always shows "no integrations running", while clearly there are
active integrations according to Gerrit. Bug or feature?
Thanks,
Marc
--
Marc Mutz | Senior Software Engineer
20 matches
Mail list logo
