Re: [Development] Qt 5.10 beta 3 released

2017-11-08 Thread Mat Sutcliffe
On 8 November 2017 at 21:27, Konstantin Tokarev wrote: > 09.11.2017, 00:20, "Thiago Macieira" : > > There was another thread since then that discussed that. I remember the > > conclusion, but not the details. > > Here it is: > > http://lists.qt-project.org/pipermail/development/2017-June/030178.h

Re: [Development] Qt 5.10 beta 3 released

2017-11-08 Thread Mat Sutcliffe
On 8 November 2017 at 19:31, Thiago Macieira wrote: > On Wednesday, 8 November 2017 10:21:05 PST Mat Sutcliffe wrote: > > Could you please elaborate on the problems that were found? > > Sorry, I don't remember. Probably something related to the fact that > constexpr >

Re: [Development] Qt 5.10 beta 3 released

2017-11-08 Thread Mat Sutcliffe
On 8 November 2017 at 15:24, Thiago Macieira wrote: > On Wednesday, 8 November 2017 01:06:51 PST Roland Winklmeier wrote: > > One question: How likely are the chances that the prebuilt MSVC 32 bit > > packages will be built with MSVC 2017 instead of 2015? As far as I know, > > the v140 toolset in

Re: [Development] QtCS 2017 logging/tracing session notes

2017-10-10 Thread Mat Sutcliffe
On 10 October 2017 at 15:28, Thiago Macieira wrote: > On Tuesday, 10 October 2017 15:12:52 CEST Christian Gagneraud wrote: > > > (PS: I don't even know if qDebug streaming is lock-free and i'm > > interested to know the answer:)) > > It's not. There are mutexes inside. > The SO answer and its co

Re: [Development] [Qt-Quick] GridStar layout for QML

2017-05-28 Thread Mat Sutcliffe
I don't see a copyright license. On 28 May 2017 at 04:00, Casey Sanchez wrote: > I've created a grid layout that I find to be more functional than the > default that is provided. > > For full documentation please see: > https://forum.qt.io/topic/64699/gridstar-layout > > The Git Repo can be fou

Re: [Development] Proposal for Qt 5.10 platforms and configurations changes

2017-04-29 Thread Mat Sutcliffe
On 29 April 2017 at 21:31, Thiago Macieira wrote: > On Friday, 28 April 2017 12:50:41 -03 Mat Sutcliffe wrote: > > tldr: MSVC expects to see linker symbols for inline member functions of > > exported classes. When such a function is defined within #ifdef > > Q_COMPILER_foo (

Re: [Development] Proposal for Qt 5.10 platforms and configurations changes

2017-04-28 Thread Mat Sutcliffe
On 28 April 2017 at 13:51, Benjamin TERRIER wrote: > 2017-04-28 14:23 GMT+02:00 Thiago Macieira : > > On Friday, 28 April 2017 03:56:22 -03 Jani Heikkinen wrote: > >> Yes, MSVC 2017 is already supported in Qt 5.9 and we are trying to get > >> pre-built binaries available before final release; le

Re: [Development] Request moving project (noron) to playground area

2017-02-24 Thread Mat Sutcliffe
Until the link is added, you can visit the direct URL http://doc-snapshots.qt.io/qt5-5.9/qtremoteobjects-index.html ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Focusing bug fixes to 5.9 branch and patch releases during H1/17

2017-02-18 Thread Mat Sutcliffe
On 18 February 2017 at 20:40, Thiago Macieira wrote: > > Hindsight is 20/20. Let's not rehash coulda-woulda-shoulda. > > The question is only what to do now. > Oh, absolutely. I just thought it might help to understand a little more how we got here. __

Re: [Development] Focusing bug fixes to 5.9 branch and patch releases during H1/17

2017-02-18 Thread Mat Sutcliffe
On 18 February 2017 at 19:13, Thiago Macieira wrote: > On sábado, 18 de fevereiro de 2017 06:36:07 PST Mat Sutcliffe wrote: > > Keeping 5.9.0 on schedule even while 5.8.0 blows past its planned release > > date would seem to be appropriate when you have the capability to &

[Development] Focusing bug fixes to 5.9 branch and patch releases during H1/17

2017-02-18 Thread Mat Sutcliffe
The upcoming process changes are very welcome. Regarding MSVC 2015/2017 ABI, I already opened QTCREATORBUG-17740. At the risk of simply repeating what others have said, it feels unsatisfying that a delay in the release of 5.8.0 should lead to a shortening of the 5.9.0 release schedule, or that in