Em segunda-feira, 17 de abril de 2017, às 21:58:51 PDT, Jani Heikkinen
escreveu:
> I agree. But on the other hand there is that many changes already in and
> quite long time since we tested this release and that's why we surely need
> time to test & fix the remaining things before we are ready for
> -Original Message-
> From: Development [mailto:development-bounces+jani.heikkinen=qt.io@qt-
> project.org] On Behalf Of Thiago Macieira
> Sent: torstaina 13. huhtikuuta 2017 22.48
> To: development@qt-project.org; releas...@qt-project.org
> Subject: Re: [Development] Qt 5.10 schedule prop
Em segunda-feira, 17 de abril de 2017, às 18:46:02 PDT, Kuba Ober escreveu:
> Are -static -ltcg -debug-and-release x86 builds tested and supported?
No and we will not test it. That will create a .lib file with no code. Only
during the linking of your application will ALL the code be generated.
Are -static -ltcg -debug-and-release x86 builds tested and supported? It seems
that they are broken on at least MSVC 2015 and 2017, in both 5.7 and 5.8.
That's using most recent production releases of either version of MSVC (no
prereleases etc), and I build using most recent jom.
For me; 5.8 in
On segunda-feira, 17 de abril de 2017 15:05:30 PDT Kevin Kofler wrote:
> Thiago Macieira wrote:
> > So src/widgets/styles/qgtkstyle.cpp did not compile with Gtk3?
>
> No, it doesn't. The GTK+ 3 theming API is very different.
>
> Some Red Hat / Fedora developers have ported the Adwaita style (the
Thiago Macieira wrote:
> So src/widgets/styles/qgtkstyle.cpp did not compile with Gtk3?
No, it doesn't. The GTK+ 3 theming API is very different.
Some Red Hat / Fedora developers have ported the Adwaita style (the default
GNOME 3 style) to Qt natively, and that is chosen by default on GNOME 3 in
Alejandro Exojo wrote:
> You should really explain which kind of code did you change, because just
> recently I adjusted code from using a key press event to a touch event,
> and the point had to change from QPoint to QPointF, and the changes were
> minimal. This wasn't explained to me, but I just
On segunda-feira, 17 de abril de 2017 11:19:42 PDT Sérgio Martins wrote:
> On Mon, Apr 17, 2017 at 6:50 PM, Thiago Macieira
>
> wrote:
> > Looks like we moved important functionality from qtbase to qtstyleplugins.
> > Why wasn't it added to .gitmodules and included in the 5.7.0 and 5.8.0
> > rele
17.04.2017, 21:20, "Sérgio Martins" :
> On Mon, Apr 17, 2017 at 6:50 PM, Thiago Macieira
> wrote:
>> Looks like we moved important functionality from qtbase to qtstyleplugins.
>> Why
>> wasn't it added to .gitmodules and included in the 5.7.0 and 5.8.0 releases?
>
> IIRC, the gtk2 stuff was c
On Mon, Apr 17, 2017 at 6:50 PM, Thiago Macieira
wrote:
> Looks like we moved important functionality from qtbase to qtstyleplugins. Why
> wasn't it added to .gitmodules and included in the 5.7.0 and 5.8.0 releases?
IIRC, the gtk2 stuff was considered non-important (there's was a
thread about thi
Looks like we moved important functionality from qtbase to qtstyleplugins. Why
wasn't it added to .gitmodules and included in the 5.7.0 and 5.8.0 releases?
Can we fix it for 5.9.0?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Em segunda-feira, 17 de abril de 2017, às 10:33:06 PDT, Jason H escreveu:
> After some more thought, I think what I need are C++ templates. So let me
> rephrase: Why not QRect and QRect?
We should do that. See André P's email.
> Also I'm still not sure though why there isn't an interface for
> QV
Em segunda-feira, 17 de abril de 2017, às 09:48:26 PDT, Marc Mutz escreveu:
> On Monday 17 April 2017 18:08:20 Thiago Macieira wrote:
> > Em segunda-feira, 17 de abril de 2017, às 00:30:23 PDT, Marc Mutz
escreveu:
> > > The problem with QT_STRICT_ITERATORS is _not_ that they are changing
> > > beg
> Sent: Monday, April 17, 2017 at 3:30 AM
> From: "Alejandro Exojo"
> To: development@qt-project.org
> Subject: Re: [Development] Lack of base classes/interfaces? Q*, Q*F
>
> On Monday 17 April 2017 03:25:49 Jason H wrote:
> > I am wondering why all the Q* and Q*F classes (where $1 in [Rect, Poi
On Monday 17 April 2017 18:08:20 Thiago Macieira wrote:
> Em segunda-feira, 17 de abril de 2017, às 00:30:23 PDT, Marc Mutz escreveu:
> > The problem with QT_STRICT_ITERATORS is _not_ that they are changing
> > begin() and end(),
>
> Actually, it was. You can't use QT_STRICT_ITERATORS in one TU an
Em segunda-feira, 17 de abril de 2017, às 00:30:23 PDT, Marc Mutz escreveu:
> The problem with QT_STRICT_ITERATORS is _not_ that they are changing begin()
> and end(),
Actually, it was. You can't use QT_STRICT_ITERATORS in one TU and not in
other, regardless of exporting or not.
--
Thiago Maci
Em segunda-feira, 17 de abril de 2017, às 04:24:25 PDT, Konstantin Tokarev
escreveu:
> 1. Is it still legal to incorporate "inline functions and templates" into
> code not covered by LGPLv3? In particular, I'm interested in qAsConst
The LGPLv3 text contains the equivalent exception. See LICENSE.L
On 16/04/2017 21:13, Olivier Goffart wrote:
>
> Q_GADGET's overhead is basically the cost of the QMetaObject. So it's there,
> but it's quite small.
> If there is an use for a class to be a Q_GADGET, I think it should be added.
For the record:
https://codereview.qt-project.org/#/c/191777/
Ciao,
Op 17/04/2017 om 12:31 schreef André Pönitz:
> On Mon, Apr 17, 2017 at 08:10:28AM +0200, André Somers wrote:
>>
>>> You're right I don't know how C++ handles virtuals, but should I
>>> care? This is OOP, I want to use OOP. You're telling me that because
>>> the language/compiler implements someth
On Mon, Apr 17, 2017 at 08:10:28AM +0200, André Somers wrote:
> Op 17/04/2017 om 08:02 schreef Jason H:
> > Maybe templates are the way to go. But I just had to change some
> > lines because I was using vectors and Qt was using QList. I'd like
> > to eliminate the need/cost for QList::toVector() an
Hello,
There is LGPL_EXCEPTION.txt that says:
-
As an additional permission to the GNU Lesser General Public License version
2.1, the object code form of a "work that uses the Library" may incorporate
material from a header file that is part of the Library. You may distribute
such ob
On Monday 17 April 2017 00:59:55 Thiago Macieira wrote:
> Em domingo, 16 de abril de 2017, às 15:16:54 PDT, Mark Gaiser escreveu:
> > Ohh, that's great!
> >
> >
> >
> > One question. Would it be possible and sane to - by default - provide
> > it as the patch implements it there, but with the addit
On Monday 17 April 2017 03:25:49 Jason H wrote:
> I am wondering why all the Q* and Q*F classes (where $1 in [Rect, Point,
> etc]) don't use an interface? I recently moved some code from ints to
> floats, and I had to change far more code than I should have had to.
>
> My proposal is to change QRe
23 matches
Mail list logo
