On quarta-feira, 28 de setembro de 2016 01:22:33 PDT Allan Sandfeld Jensen
wrote:
> > QVariant::fromValue(nullptr).isNull() == false
> > QVariant(QMetaType::Nullptr).isNull() == true
>
> And QVariant(nullptr) doesn't compile.
>
> We should probably fix the fromValue constructor.
I don't think s
Thanks Thiago and Jake,
When Coin is expected to be released? I was thinking if it is very close
then we can continue using our current infrastructure, otherwise we will
implement something similar to Coin.
I found information about Coin on qt blog and testresults overview page
very helpful. It g
> On Sep 27, 2016, at 3:00 PM, Thiago Macieira
> wrote:
>
> On terça-feira, 27 de setembro de 2016 19:27:07 PDT Liang Qi wrote:
>>> I search over google and checked code.qt.io/cgit/ but could not find COIN
>>> scripts. Is it public domain? Let me know if someone knows the repo link.
>>
>> http
On Tuesday 27 September 2016, Thiago Macieira wrote:
> On terça-feira, 27 de setembro de 2016 18:22:34 PDT Simon Hausmann wrote:
> > I'm fairly sure we used QVariant(QMetaType::VoidStar);
>
> Can you guarantee that the only time the QML engine generates null
> QVariants is for null JS Values? That
On terça-feira, 27 de setembro de 2016 19:27:07 PDT Liang Qi wrote:
> > I search over google and checked code.qt.io/cgit/ but could not find COIN
> > scripts. Is it public domain? Let me know if someone knows the repo link.
>
> https://blog.qt.io/blog/2016/08/08/coin-continuous-integration-for-qt/
On terça-feira, 27 de setembro de 2016 18:22:34 PDT Simon Hausmann wrote:
> I'm fairly sure we used QVariant(QMetaType::VoidStar);
Can you guarantee that the only time the QML engine generates null QVariants
is for null JS Values? That is, no null QStrings, null QVariantLists, null
QVariantMaps/
I'm fairly sure we used QVariant(QMetaType::VoidStar);
Simon
From: thiago.macie...@intel.com
Sent: September 27, 2016 19:26
To: development@qt-project.org
Subject: Re: [Development] Behaviour change in QML in Qt 5.8 regarding null
On terça-feira, 27 de setembro de 2016 09:31:14 PDT Thiago Mac
Thanks Liang,
Regards,
Manish
On Tue, Sep 27, 2016 at 10:57 PM Liang Qi wrote:
> On 27 September 2016 at 19:23, manish sharma <83.man...@gmail.com> wrote:
>
>> Hi,
>>
>> I am working on a project which consists of around 20 git submodules and
>> we use jenkins as our CI. I was searching for an
On 27 September 2016 at 19:23, manish sharma <83.man...@gmail.com> wrote:
> Hi,
>
> I am working on a project which consists of around 20 git submodules and
> we use jenkins as our CI. I was searching for an alternative to manage
> builds and I came across COIN scripts which qt uses to run its CI.
On terça-feira, 27 de setembro de 2016 09:31:14 PDT Thiago Macieira wrote:
> On terça-feira, 27 de setembro de 2016 15:29:16 PDT Simon Hausmann wrote:
> > That said, I think it can be written without #ifdef perhaps by using
> > QVariant::isNull() ?
> >
> >
> > (QVariant(nullptr) maps to isNull()
Hi,
I am working on a project which consists of around 20 git submodules and we
use jenkins as our CI. I was searching for an alternative to manage builds
and I came across COIN scripts which qt uses to run its CI. And it
perfectly suits our requirement especially dependency resolver and storage.
On terça-feira, 27 de setembro de 2016 15:29:16 PDT Simon Hausmann wrote:
> That said, I think it can be written without #ifdef perhaps by using
> QVariant::isNull() ?
>
>
> (QVariant(nullptr) maps to isNull() as well, right? ;-)
It should.
But QVariant(QString()) [after you bypass C++'s most v
Hi,
I'm personally fine with delaying this by one release. What do others think?
That said, I think it can be written without #ifdef perhaps by using
QVariant::isNull() ?
(QVariant(nullptr) maps to isNull() as well, right? ;-)
Simon
From: Development on
On terça-feira, 27 de setembro de 2016 11:25:49 PDT Simon Hausmann wrote:
> That is exactly the part I'm referring to. Receiving a QVariant from the QML
> engine and relying on it to contain a specific type.
Well, I would say it's acceptable that the QVariant contain different numeric
types as th
Hi,
That is exactly the part I'm referring to. Receiving a QVariant from the QML
engine and relying on it
to contain a specific type.
Simon
From: Thiago Macieira
Sent: Monday, September 26, 2016 8:14:58 PM
To: development@qt-project.org
Cc: Simon Hausmann
S
Jędrek said:
> Friendly reminder about dropping support for sync.profile in favor of
> .gitmodules. The new code will be deployed on on Wednesday (28.09.2016) unless
> I will find some major breakages to that point.
... and, just to avoid any confusion, that's only the dependencies
between module
16 matches
Mail list logo