Similar to the header diffs, each minor version the .qmltypes files
for QML plugins gets updated and that diff
(https://codereview.qt-project.org/#change,70479) should show
everything that snuck into public QML APIs. I put my comments on
gerrit, it's better for inline review of code diffs. But it r
On Tue, 05 Nov 2013 14:12:37 +, Koehne Kai wrote:
> See http://qt-project.org/wiki/Building_Qt_5_from_Git
>
> You need to basically install all libxcb-* packages
Thanks a lot, I'll try it.
Regards
___
Development mailing list
Development@qt-proj
On 06/11/13 13:19, Liang Qi wrote:
> On Wednesday 06 November 2013 12:17:56 Christian Gagneraud wrote:
>> Hi,
>>
>> I'm using CLang build-analize tool, and when I switched from Qt 4.8 to
>> Qt 5.1 (insalled from Qt project's download area), I got a Qt #error,
>> basically the code is built with -fP
On 06/11/13 12:25, Olivier Goffart wrote:
> On Wednesday 06 November 2013 12:17:56 Christian Gagneraud wrote:
>> Hi,
>>
>> I'm using CLang build-analize tool, and when I switched from Qt 4.8 to
>> Qt 5.1 (insalled from Qt project's download area), I got a Qt #error,
>> basically the code is built w
On Wednesday 06 November 2013 12:17:56 Christian Gagneraud wrote:
> Hi,
>
> I'm using CLang build-analize tool, and when I switched from Qt 4.8 to
> Qt 5.1 (insalled from Qt project's download area), I got a Qt #error,
> basically the code is built with -fPIC, but CLang doesn't define a PIC
> macro
On quarta-feira, 6 de novembro de 2013 12:17:56, Christian Gagneraud wrote:
> I'm using CLang build-analize tool, and when I switched from Qt 4.8 to
> Qt 5.1 (insalled from Qt project's download area), I got a Qt #error,
> basically the code is built with -fPIC, but CLang doesn't define a PIC
>
On Wednesday 06 November 2013 12:17:56 Christian Gagneraud wrote:
> Hi,
>
> I'm using CLang build-analize tool, and when I switched from Qt 4.8 to
> Qt 5.1 (insalled from Qt project's download area), I got a Qt #error,
> basically the code is built with -fPIC, but CLang doesn't define a PIC
> macr
Hi,
I'm using CLang build-analize tool, and when I switched from Qt 4.8 to
Qt 5.1 (insalled from Qt project's download area), I got a Qt #error,
basically the code is built with -fPIC, but CLang doesn't define a PIC
macro, so the build fails due to a check in qglobal.h (see details below).
Is
On 05/11/13 21:58, "André Pönitz"
wrote:
>On Mon, Nov 04, 2013 at 08:49:45PM -0800, Alan Alpert wrote:
>> >> > As some of you may know, Shane has a new job and therefore has a
>>lot
>> >> > less time to spend on QtNetwork. He, Peter and I have discussed how
>> >> > we should maintain the module i
On Monday 04 November 2013 11:55:49 Thiago Macieira wrote:
> On segunda-feira, 4 de novembro de 2013 18:21:38, Knoll Lars wrote:
> > I¹m also happy that Peter and Rich are stepping up to take over the
> > maintainership. A shared maintainership is something we didn¹t have
> > before, but I¹m happy
On Mon, Nov 04, 2013 at 08:49:45PM -0800, Alan Alpert wrote:
> >> > As some of you may know, Shane has a new job and therefore has a lot
> >> > less time to spend on QtNetwork. He, Peter and I have discussed how
> >> > we should maintain the module in the future. What we're proposing is
> >> > that
Module looks ok. Some comment inline:
On 05/11/13 01:07, "Thiago Macieira" wrote:
>Pastebin URL (expires in 24 hours):
>http://paste.fedoraproject.org/51637/13836114
>
>template
> QObject *qmlAttachedPropertiesObject(const QObject *obj, bool create =
>true)
> {
>diff --git a/src/qml/qml/qqmlcomp
Looks ok as well.
Cheers,
Lars
On 05/11/13 01:07, "Thiago Macieira" wrote:
>Pastebin URL (expires in 24 hours):
>http://paste.fedoraproject.org/51638/61143313
>
>---
>diff --git a/src/quick/designer/designersupport.h
>b/src/quick/designer/designersupport.h
>index 5139a65..41458ae 100644
>--- a
For WiFi Direct, I see a similarity with QAbstractSocket API.
Here is the documentation of QAbstractSocket::connectToHost method:
***
void QAbstractSocket::connectToHost(const QString & hostName, quint16 port,
OpenMode openMode = ReadWrite, NetworkLayerProtocol protocol = AnyIPProtocol)
[virtual]
IIRC it wasn't even compiled into the QtWidgets library, although the
documentation and everything existed, those symbols were never in Qt. Morten
can say 100% at least but that is my understanding and recollection at least.
Andy
From: development-bounces+andy.shaw=digia@qt-project.org
[ma
On Nov 5, 2013, at 12:55 PM, Thiago Macieira wrote:
> On terça-feira, 5 de novembro de 2013 12:39:55, Jake Petroules wrote:
>> On Nov 5, 2013, at 12:22 PM, Marc Mutz wrote:
>>> But can be overloaded on the new types, right.
>>
>> Does this 100% NEED to be reverted? It wasn't even functional unt
On terça-feira, 5 de novembro de 2013 12:39:55, Jake Petroules wrote:
> On Nov 5, 2013, at 12:22 PM, Marc Mutz wrote:
> > But can be overloaded on the new types, right.
>
> Does this 100% NEED to be reverted? It wasn't even functional until 5.2
> IIRC.
>
> I really hope this does not have to wai
On Nov 5, 2013, at 12:22 PM, Marc Mutz wrote:
> On Tuesday, November 05, 2013 17:51:25 Thiago Macieira wrote:
>> On terça-feira, 5 de novembro de 2013 11:09:48, Giuseppe D'Angelo wrote:
class Q_WIDGETS_EXPORT QMacCocoaViewContainer : public QWidget
{
Q_OBJECT
>>>
On Tuesday 05 November 2013 10:51:54 Nowacki Jedrzej wrote:
> It changes the public interface depending on QT_NO_DEBUG_STREAM which is
> suboptimal especially that even if the flag is specified QDebug is defined.
We don't support binary compatibility when feature are disabled via QT_NO_*
And we c
On Tuesday, November 05, 2013 17:51:25 Thiago Macieira wrote:
> On terça-feira, 5 de novembro de 2013 11:09:48, Giuseppe D'Angelo wrote:
> > > class Q_WIDGETS_EXPORT QMacCocoaViewContainer : public QWidget
> > > {
> > >
> > > Q_OBJECT
> > >
> > > public:
> > > -QMacCocoaViewCo
Agreed with Jake. If ICNS files support doesn't require platform API calls,
let's simply add it and give the user an options.
That's quite the same as ICO files support: are they common/required on
Linux? - No. Are they supported? - Yes, optionally.
And since we're in Open Governance area, maybe K
05.11.2013, 21:19, "Konstantin Ritt" :
> That's quite the same as ICO files support: are they common/required on
> Linux? - No. Are they supported? - Yes, optionally.
favicon.ico
--
Regards,
Konstantin
___
Development mailing list
Development@qt-proj
On terça-feira, 5 de novembro de 2013 18:10:30, Marc Mutz wrote:
> Any integer type would previously pick the (int) ctor. Now, everything
> except int and qint64 will be ambiguous, in particular unsigned int.
>
> Hmm, or maybe the (bool) overload already made everything other than int
> and bool
On Tuesday, November 05, 2013 14:32:03 John Layt wrote:
> On 5 November 2013 12:03, Marc Mutz wrote:
> > On Tuesday, November 05, 2013 01:07:32 Thiago Macieira wrote:
> >> +// ### Qt 6: Merge with above with default offsetSeconds = 0
> >> +QDateTime(const QDate &date, const QTime &time, Qt
On Tuesday, November 05, 2013 17:42:38 Thiago Macieira wrote:
> I think that was intentional since JSON is still using ECMAScript data
> types, whose Number type is a double precision floating point. Inserting
> any integer larger than 2^52 will result in loss of precision. So this
> forces people
On Tuesday, November 05, 2013 18:00:02 Nicolás Alvarez wrote:
> 2013/11/5 Marc Mutz :
> > On Tuesday, November 05, 2013 01:07:32 Thiago Macieira wrote:
> >> -return (void *)qptrdiff(data);
> >> +char *null = 0;
> >> +return null + qptrdiff(data);
> >
> > Since t
On 5 Nov 2013, at 5:47 PM, Jake Petroules wrote:
> I do. Qt is by nature a cross platform framework, limiting support for ICNS
> files only to OS X doesn't really make sense.
>
> What if you want to create a cross platform icon editor or some other app
> that deals with image files? Or reuse y
> >
> > It could also fail later, as it is mostly asynchronous. Or it could
> succeed with a result. ie
> >
> > Q_SIGNAL void deviceConntected(SomeDevice device);
> > Q_SIGNAL void deviceConnectionFailed(SomeOtherConnectError
> error);
> >
> > or one signal:
> >
> > Q_SIGNAL void device
2013/11/5 Marc Mutz :
> On Tuesday, November 05, 2013 01:07:32 Thiago Macieira wrote:
>> -return (void *)qptrdiff(data);
>> +char *null = 0;
>> +return null + qptrdiff(data);
>
> Since this is equivalent to
>
> return 0[qptrdiff(data)];
>
> isn't that derefer
On terça-feira, 5 de novembro de 2013 12:24:32, Marc Mutz wrote:
> On Tuesday, November 05, 2013 01:07:32 Thiago Macieira wrote:
> > -return (void *)qptrdiff(data);
> > +char *null = 0;
> > +return null + qptrdiff(data);
>
> Since this is equivalent to
>
>
On terça-feira, 5 de novembro de 2013 11:09:48, Giuseppe D'Angelo wrote:
> > +#ifdef Q_OS_OSX
> > +NSMenu* toNSMenu();
> > +void setAsDockMenu();
> > +#endif
>
> Is it OK to reintroduce platform specific calls in the APIs? I would've
> expected this kind of functionality to be provided by
On terça-feira, 5 de novembro de 2013 11:09:48, Giuseppe D'Angelo wrote:
> > class Q_WIDGETS_EXPORT QMacCocoaViewContainer : public QWidget
> > {
> > Q_OBJECT
> >
> > public:
> > -QMacCocoaViewContainer(void *cocoaViewToWrap, QWidget *parent = 0);
> > +QMacCocoaViewContainer(NSV
I do. Qt is by nature a cross platform framework, limiting support for ICNS
files only to OS X doesn't really make sense.
What if you want to create a cross platform icon editor or some other app that
deals with image files? Or reuse your OS X icon(s) on Windows and other
platforms, saving time
On terça-feira, 5 de novembro de 2013 11:22:45, Marc Mutz wrote:
> On Tuesday, November 05, 2013 01:07:32 Thiago Macieira wrote:
> > @@ -206,7 +212,8 @@ protected:
> > int qt4D;
> > Qt::Orientation qt4O;
> > Qt::MouseButtons mouseState;
> >
> > -int reserved;
> > +uint ph :
On terça-feira, 5 de novembro de 2013 12:05:13, Marc Mutz wrote:
> This just adds missing implementation, it's rediculous not to backport to
> 5.1, is it?
Backporting to 5.1 would be safe, indeed.
But it's not urgent. Anyone trying to use those methods has failed to compile,
so it's not a regre
On terça-feira, 5 de novembro de 2013 11:44:41, Marc Mutz wrote:
> On Tuesday, November 05, 2013 01:07:32 Thiago Macieira wrote:
> > diff --git a/src/corelib/json/qjsonvalue.h b/src/corelib/json/qjsonvalue.h
> > index b8bdf55..c0ecdd2 100644
> > --- a/src/corelib/json/qjsonvalue.h
> > +++ b/src/cor
On Nov 5, 2013, at 5:12 PM, Tony Van Eerd wrote:
> Most of BlackBerry's APIs are async.
> We are looking at moving some of these APIs into Qt.
> Just as one example, WiFi Direct.
>
> I have been attempting to come up with some solid guidelines of how to deal
> with errors on async operations.
On terça-feira, 5 de novembro de 2013 10:51:54, Nowacki Jedrzej wrote:
> I looked into qmetatype.h. There is a lot of new symbols most of them hidden
> in a private namspace. None symbol was removed. I believe BC is fine.
The library BC might be fine. The question is to verify whether the metatype
On terça-feira, 5 de novembro de 2013 08:57:12, Saether Jan-Arve wrote:
> Is there any big benefits in having ICNS support on other platforms than
> OSX?
I don't think anyone wants ICNS outside OS X. But JPEG2000 might be useful.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Arc
Most of BlackBerry's APIs are async.
We are looking at moving some of these APIs into Qt.
Just as one example, WiFi Direct.
I have been attempting to come up with some solid guidelines of how to deal
with errors on async operations.
Some things to consider:
- the initial request may fail. ie
On Tue, Nov 5, 2013 at 10:56 AM, Sorvig Morten wrote:
> On 02 Nov 2013, at 17:58, Thiago Macieira
> wrote:
>
> > On quarta-feira, 30 de outubro de 2013 07:29:56, Turunen Tuukka wrote:
> >> We should have the applications made with Qt 4.8.5 on Mac OS 10.7 (for
> >> example) working in 10.9 without
On 02 Nov 2013, at 17:58, Thiago Macieira wrote:
> On quarta-feira, 30 de outubro de 2013 07:29:56, Turunen Tuukka wrote:
>> We should have the applications made with Qt 4.8.5 on Mac OS 10.7 (for
>> example) working in 10.9 without serious issues. And we should be able to
>> agree together what i
Thankfully we don't bother with platforms where sizeof(int)! = 4. But out of
curiosity, which platforms nowadays use for example smaller sizes? Some 16-bit
micro controllers?
Simon
Fra: Giuseppe D'Angelo
Sendt: 02:32 tirsdag 5. november 2013
Til: development@qt-project.org
Emne: Re: [Developme
> -Original Message-
> From: development-bounces+kai.koehne=digia@qt-project.org
> [mailto:development-bounces+kai.koehne=digia@qt-project.org] On
> Behalf Of Hongyi Zhao
> Sent: Tuesday, November 05, 2013 1:48 PM
> To: development@qt-project.org
> Subject: [Development] If I not u
On 5 November 2013 12:03, Marc Mutz wrote:
> On Tuesday, November 05, 2013 01:07:32 Thiago Macieira wrote:
>> +// ### Qt 6: Merge with above with default offsetSeconds = 0
>> +QDateTime(const QDate &date, const QTime &time, Qt::TimeSpec spec, int
>> offsetSeconds);
>> +#ifndef QT_BOOTSTRAP
On Tuesday, November 05, 2013 12:24:32 Marc Mutz wrote:
> What's wrong with
>
>reinterpret_cast(qptrdiff(data));
-> https://codereview.qt-project.org/70402
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/l
Hi,
We are about to start "Qt 5.2.0 RC1" release, which means that:
- We plan to do a fast-forward merge from 'stable' into 'release' branch
on Nov 11th. So no CI involved here [1].
- After Nov 11th any changes that are required for 5.2.0 need to be
pushed to the 'release' branch. So if your cha
Hi all,
I try to compile qt-everywhere-opensource-src-5.1.1 on Debian Wheezy, I
find I must use the following commands otherwise it will failed to make:
$ ./configure -qt-xcb && make && sudo make install
I just cann't remember the error messages if I don't use the -qt-xcb
option.
Who can gi
On Mon, Nov 04, 2013 at 11:47:27AM -0800, Thiago Macieira wrote:
> On segunda-feira, 4 de novembro de 2013 19:46:57, Oswald Buddenhagen wrote:
> > in that light i find it quite important to be able to judge the
> > threshold of copyright relevance ourselves.
>
> Please contact the legal department
On Tue, 05 Nov 2013 16:35:25 +0400, Konstantin Tokarev wrote:
> Install binutils-gold.
I've installed it but the issue still as it was. The following give you
the info of binutils-gold on my box:
--
werner@debian-asus:~$ ld --version
GNU gold (GNU Binutils for Debian 2.22) 1.11
Copyright 2
05.11.2013, 11:15, "Hongyi Zhao" :
> Hi all,
>
> I use Debian Wheezy, and I build qt-everywhere-opensource-src-4.8.5
> failed with the following error:
>
> -
> g++: error: unrecognized command line option ‘-fuse-ld=gold’
> g++: error: unrecognized command line option ‘-fuse-ld=gold’
>
On Tue, 05 Nov 2013 11:54:57 +, Bruning Michael wrote:
> I suppose you are using GCC version 4.7 or newer
Yes, see the following for detail:
werner@debian-asus:~$ gcc --version
gcc (Debian 4.7.2-5) 4.7.2
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source
On Tuesday 05 November 2013 12:24:32 Marc Mutz wrote:
> On Tuesday, November 05, 2013 01:07:32 Thiago Macieira wrote:
> > -return (void *)qptrdiff(data);
> > +char *null = 0;
> > +return null + qptrdiff(data);
>
> Since this is equivalent to
>
> return 0[qp
Hello,
On Tuesday, 5th November 2013 at 08:02 am, Hongyi Zhao wrote:
>
>
> Hi all,
>
> I use Debian Wheezy, and I build qt-everywhere-opensource-src-4.8.5 failed
> with the following error:
>
> -
> g++: error: unrecognized command line option ‘-fuse-ld=gold’
> g++: error: unrecogn
On Tuesday, November 05, 2013 01:07:32 Thiago Macieira wrote:
> -return (void *)qptrdiff(data);
> +char *null = 0;
> +return null + qptrdiff(data);
Since this is equivalent to
return 0[qptrdiff(data)];
isn't that dereferencing the nullptr and therefore und
On Tuesday, November 05, 2013 01:07:32 Thiago Macieira wrote:
> +++ b/src/corelib/tools/qmargins.h
> @@ -242,6 +242,24 @@ inline QMargins &QMargins::operator-=(const QMargins
> &margins) return *this = *this - margins;
> }
>
> +inline QMargins &QMargins::operator+=(int margin)
> +{
> +m_left
On Tuesday, November 05, 2013 01:07:32 Thiago Macieira wrote:
> +// ### Qt 6: Merge with above with default offsetSeconds = 0
> +QDateTime(const QDate &date, const QTime &time, Qt::TimeSpec spec, int
> offsetSeconds);
> +#ifndef QT_BOOTSTRAPPED
> +QDateTime(const QDate &date, const QTim
On segunda-feira, 4 de novembro de 2013 16:07:32, Thiago Macieira wrote:
> I didn't find anything, but I did not review qmetatype.h.
I looked into qmetatype.h. There is a lot of new symbols most of them hidden in
a private namspace. None symbol was removed. I believe BC is fine.
I see one potent
On 11/05/2013 04:38 AM, Thiago Macieira wrote:
> On segunda-feira, 4 de novembro de 2013 16:07:32, Thiago Macieira wrote:
>> +QByteArray session() const;
>> +void setSession(const QByteArray &session);
>> +int sessionTicketLifeTimeHint() const;
>
> Module is fine.
>
> I'm just wondering
On Tuesday, November 05, 2013 01:07:32 Thiago Macieira wrote:
> diff --git a/src/corelib/json/qjsonvalue.h b/src/corelib/json/qjsonvalue.h
> index b8bdf55..c0ecdd2 100644
> --- a/src/corelib/json/qjsonvalue.h
> +++ b/src/corelib/json/qjsonvalue.h
> @@ -79,6 +79,7 @@ public:
> QJsonValue(bool b
Il 05/11/2013 11:22, Marc Mutz ha scritto:
On Tuesday, November 05, 2013 01:07:32 Thiago Macieira wrote:
@@ -206,7 +212,8 @@ protected:
int qt4D;
Qt::Orientation qt4O;
Qt::MouseButtons mouseState;
-int reserved;
+uint ph : 2;
+int reserved : 30;
};
#endif
is s
On Tuesday, November 05, 2013 01:07:32 Thiago Macieira wrote:
> @@ -101,9 +102,10 @@ public:
> {
> if (dirty) {
> dirty = false;
> -QVector sorted = values;
> -qSort(sorted);
> -currentMedian = sorted.at(bufferSize / 2 + 1);
> +
On Tuesday, November 05, 2013 01:07:32 Thiago Macieira wrote:
> @@ -206,7 +212,8 @@ protected:
> int qt4D;
> Qt::Orientation qt4O;
> Qt::MouseButtons mouseState;
> -int reserved;
> +uint ph : 2;
> +int reserved : 30;
> };
> #endif
is sizeof(int) == 4 everywhere?
> ---
On 4 Nov 2013, at 10:51 PM, Mikkel Krautz wrote:
> Hello,
>
> I'm process of attempting to integrate support for the ICNS (OS X icon
> files) format into Qt as an icon engine.
> (https://codereview.qt-project.org/#change,60290)
>
> An optional, but desirable part of the ICNS format is support f
On 5 Nov 2013, at 8:04 pm, Peter Hartmann wrote:
> Hello,
>
> I also think having 2 maintainers versus 1 maintainer for QtNetwork will
> not matter much in practice; but if people demand to have one single
> go-to person I am also fine with either of us taking that role.
>
I don't have a pr
Il 05/11/2013 01:07, Thiago Macieira ha scritto:
Pastebin URL (expires in 24 hours):
http://paste.fedoraproject.org/51643/61145013
---
diff --git a/src/widgets/dialogs/qcolordialog.h
b/src/widgets/dialogs/qcolordialog.h
index 80a31c4..c7a1d6f 100644
--- a/src/widgets/dialogs/qcolordialog.h
+++
Hello,
I also think having 2 maintainers versus 1 maintainer for QtNetwork will
not matter much in practice; but if people demand to have one single
go-to person I am also fine with either of us taking that role.
Peter
On 11/04/2013 09:38 PM, Richard Moore wrote:
> Hi All,
>
> I think there's
On 5 November 2013 05:09, Yuchen Deng wrote:
> The ICU dependency is very heavy, I did not like it.
> Is there any possible to make the ICU depend is optional?
> Thanks!
Sorry, it is not possible to remove the dependency, all you can do is
to reduce the size of ICU by not shipping data you don't
Hi
I'm just wondering if we need yet another library (Jasper), therefore my
question:
Is there any big benefits in having ICNS support on other platforms than OSX?
Jan Arve
> -Original Message-
> From: development-bounces+jan-arve.saether=digia@qt-project.org
> [mailto:development-
On Monday, 2013-11-04, 21:48:11, Alan Alpert wrote:
> On Sat, Nov 2, 2013 at 5:06 AM, Kevin Krammer
wrote:
> > The thing is that the widgets wouldn't have non-Widget parents, at least
> > not in DeclarativeWidgets. The parent is either a widget or, most of the
> > times, a layout. The layouts' a
70 matches
Mail list logo
