On Thursday, 13 December 2018 11:57:48 PST Edward Welbourne wrote:
> Indeed, the name plusDays might have been better. With any luck we can
> fix this in Qt6 by deprecating the old methods, supporting std::chrono
> and just allowing arithmetic with appropriate std::chrono quantities, in
> the
>>> Not saying it's correct, just stating the fact that function name is
>>> confusing and potentially problematic because it doesn't do what it
>>> states it does.
Il 13/12/18 15:55, Edward Welbourne ha scritto:
>> Aye, there's plenty that isn't perfect, especially in old APIs. None
>> the
Looks like a lot of projects are now failing to compile with Qt 5.12 because
qcollectiongenerator has disappeared. The changelog simply says:
- Removed qhelpconverter tool.
- Merged qcollectiongenerator tool into the qhelpgenerator tool.
Should I simply replace "collection" with "help" in
Il 13/12/18 15:55, Edward Welbourne ha scritto:
Not saying it's correct, just stating the fact that function name is
confusing and potentially problematic because it doesn't do what it
states it does.
Aye, there's plenty that isn't perfect, especially in old APIs. None
the less, the Qt project
Hi everyone!
I am happy to announce Qt 3D Studio 2.2 was released today.
Read more information from blog post:
http://blog.qt.io/blog/2018/12/13/qt-3d-studio-2-2-released/
Big thanks to everyone involved!
br,
Jukka Jokiniva
Release Manager
The Qt Company
NIkolai Marchenko (13 December 2018 15:24)
> It's not like I don't understand all that. But I am not that person who
> introduced the regression and
>
> a) He doesn't use a compiler that supports this warning
> b) ... and he wouldn't have read it in the first place. (unfortunately)
> c) He
It's not like I don't understand all that. But I am not that person who
introduced the regression and
a) He doesn't use a compiler that supports this warning
b) ... and he wouldn't have read it in the first place. (unfortunately)
c) He doesn't much care about docs
Not saying it's correct, just
On 2018-12-13 13:48, NIkolai Marchenko wrote:
This non obvious (from function name) behaviour actually caused
infinite
loop regression in our code just recently.
The person used it inside a while loop thinking it will loop upwards
and
stop.
If your compiler supports it, you should get a
The docs [1] clearly state what the method does. Moreover, the method is
const, so it can't mutate the object.
[1] https://doc.qt.io/qt-5/qdatetime.html#addDays
Cheers
Dmitriy
On Thu, Dec 13, 2018 at 3:04 PM NIkolai Marchenko
wrote:
> This non obvious (from function name) behaviour actually
This non obvious (from function name) behaviour actually caused infinite
loop regression in our code just recently.
The person used it inside a while loop thinking it will loop upwards and
stop.
On Thu, Dec 13, 2018 at 4:45 PM Edward Welbourne
wrote:
> Fausto Papandrea (13 December 2018 12:48)
Fausto Papandrea (13 December 2018 12:48)
> Hi, I would like to understand the logic of the addDays function of
> QDateTime.
>
> I mean, why doesn't it modify the calling object, but returns a copy of
> a new object instead?
At this point, it does what it does because it's done so for years
On Thu, 13 Dec 2018 12:47:08 +0100
Kevin Kofler wrote:
> Christian Gagneraud wrote:
> > On Thu, 13 Dec 2018 at 12:27, Kevin Kofler wrote:
> >> (so, unlike QBS, it does not depend on Qt, which would mean a circular
> >> dependency when building Qt),
> >
> > qmake has this problem, yet it's
Il 07/12/18 13:46, Sze Howe Koh ha scritto:
This is a problem because the Qt docs are heavily cited in the forums,
the wiki, and external sites like StackOverflow.
On 08.12.2018 02:34, Topi Reiniö wrote:
> Redirects are now in place. We have also plans to implement better
> versioning for the
> And it would be much worse for QBS, which requires much more from Qt than
> QMake. It requires QML, JavaScript, etc.
So what? A GCC too compiles with GCC... For me, as a developer it is not a
big problem and not a my. A worse problem is in CMake's ideology.
QBS just work immediatelly! Unlike
> Once you have the cross toolchain configured properly, which is a
one-time
> setup effort, CMake will just work, too.
Will just work? What??! HAHA. Are you kidding?
Why I need to configure something? Why I need to create an additional
CMake's scripts, config files, toolchains and etc?
I
Hi, I would like to understand the logic of the addDays function of
QDateTime.
I mean, why doesn't it modify the calling object, but returns a copy of
a new object instead?
Thank you.
___
Development mailing list
Development@qt-project.org
Christian Gagneraud wrote:
> On Thu, 13 Dec 2018 at 12:27, Kevin Kofler wrote:
>> (so, unlike QBS, it does not depend on Qt, which would mean a circular
>> dependency when building Qt),
>
> qmake has this problem, yet it's been packaged for 10+ years without a
> problem.
Bootstrapping QMake has
On Thu, 13 Dec 2018 at 12:27, Kevin Kofler wrote:
Hi Kevin,
> > PS: WTF? Why the Qt's management choosed the CMake's instead of QBS?
>
> Because CMake is a widespread tool written in C++/STL
Some people are scared of the wolf, i'm scared of the sheepple.
> (so, unlike QBS, it
> does not depend
18 matches
Mail list logo
