On sábado, 7 de julho de 2012 02.12.42, Olivier Goffart wrote:
> Anyway, if we want to support that version of clang, this still need to be
> worked around, so I suggest that the problematic code should be #ifdef'd
> out for the 'broken' versions of clang.
We also need to know which version fixes
On sexta-feira, 6 de julho de 2012 21.02.20, Leandro Melo de Sales wrote:
> Hi,
> I have compiled qt5 and setup it in Qt Creator 2.4.83. But I got a
> warning "no qmlviewer found". How to fix this?
How did you compile the qtquick1 module? Did it finish with success?
--
Thiago Macieira - thiago.
On Friday 06 July 2012 17:26:13 Stephen Chu wrote:
> On 7/6/12 3:23 PM, Thiago Macieira wrote:
> > On sexta-feira, 6 de julho de 2012 14.53.56, Stephen Chu wrote:
> >> I tried Clang 3.1 and it compiles with or without the equal sign.
> >
> > Then I don't understand. If it supports brace-initialisa
Hi,
I have compiled qt5 and setup it in Qt Creator 2.4.83. But I got a
warning "no qmlviewer found". How to fix this?
[]s,
Leandro.
--
Leandro Melo de Sales
PhD candidate in Computer Science
Pervasive and Embedded Computing Laboratory, UFCG
___
Develop
On 7/6/12 3:23 PM, Thiago Macieira wrote:
> On sexta-feira, 6 de julho de 2012 14.53.56, Stephen Chu wrote:
>> I tried Clang 3.1 and it compiles with or without the equal sign.
>
> Then I don't understand. If it supports brace-initialisation for non-PODs, why
> is it complaining about QBasicAtomicI
On sexta-feira, 6 de julho de 2012 14.53.56, Stephen Chu wrote:
> I tried Clang 3.1 and it compiles with or without the equal sign.
Then I don't understand. If it supports brace-initialisation for non-PODs, why
is it complaining about QBasicAtomicInt?
--
Thiago Macieira - thiago.macieira (AT) int
On 7/6/12 2:25 PM, Thiago Macieira wrote:
> On sexta-feira, 6 de julho de 2012 13.22.38, Stephen Chu wrote:
>> On 7/6/12 12:19 PM, Thiago Macieira wrote:
>>> On sexta-feira, 6 de julho de 2012 18.12.10, Olivier Goffart wrote:
#if defined(Q_COMPILER_CONSTEXPR) && defined(Q_COMPILER_DEFAULT_MEMB
On sexta-feira, 6 de julho de 2012 13.22.38, Stephen Chu wrote:
> On 7/6/12 12:19 PM, Thiago Macieira wrote:
> > On sexta-feira, 6 de julho de 2012 18.12.10, Olivier Goffart wrote:
> >> #if defined(Q_COMPILER_CONSTEXPR) && defined(Q_COMPILER_DEFAULT_MEMBERS)
> >> &&
> >> defined(Q_COMPILER_DELETE_M
On 06/07/12 12:24, Thiago Macieira wrote:
> On sexta-feira, 6 de julho de 2012 17.08.08, Alan Alpert wrote:
>>> Most c++ developers wouldn't want to choose between stability and
>>> performance.
>>> I'm adventurous, just point me at the "qt private header forum" where
>>> interface changes are comm
On 7/6/12 1:22 PM, Stephen Chu wrote:
> On 7/6/12 12:19 PM, Thiago Macieira wrote:
>> On sexta-feira, 6 de julho de 2012 18.12.10, Olivier Goffart wrote:
>>> #if defined(Q_COMPILER_CONSTEXPR) && defined(Q_COMPILER_DEFAULT_MEMBERS) &&
>>> defined(Q_COMPILER_DELETE_MEMBERS)
>>>
>>> fixes the problem
On 7/6/12 12:19 PM, Thiago Macieira wrote:
> On sexta-feira, 6 de julho de 2012 18.12.10, Olivier Goffart wrote:
>> #if defined(Q_COMPILER_CONSTEXPR) && defined(Q_COMPILER_DEFAULT_MEMBERS) &&
>> defined(Q_COMPILER_DELETE_MEMBERS)
>>
>> fixes the problem for me.
>> So it should be disabled for those
On sexta-feira, 6 de julho de 2012 18.12.10, Olivier Goffart wrote:
> #if defined(Q_COMPILER_CONSTEXPR) && defined(Q_COMPILER_DEFAULT_MEMBERS) &&
> defined(Q_COMPILER_DELETE_MEMBERS)
>
> fixes the problem for me.
> So it should be disabled for those broken version of clang.
Looks like a compiler b
On Friday 06 July 2012 11:17:15 Stephen Chu wrote:
> Has anyone successfully build Qt 5 to use with Clang 3.1 on any
> platform? I see the new macx-clang-libc++ mkspecs are now included.
> Using it enables automatic detection of C++11 features in configure. But
> that causes errors on C++11 feature
Has anyone successfully build Qt 5 to use with Clang 3.1 on any
platform? I see the new macx-clang-libc++ mkspecs are now included.
Using it enables automatic detection of C++11 features in configure. But
that causes errors on C++11 features when building like:
animation/qabstractanimation.cpp:
What I miss is a "true" return value for
QMetaProperty::hasNotifySignal() in case of "width", "height", "x",
"y", and all the other properties when it makes sense (for all QObject
derived classes).
I know this functionality is from 4.5 or 4.6, and I thought it's not
possible to add it for existing
On 07/06/2012 03:29 PM, Thiago Macieira wrote:
> QWidget was written before properties could have NOTIFY signals. That's why
> its properties don't notify of changes.
What doesn't explain, why QWidget doesn't indicate changes of its
geometry by signals. Maybe the reason once was that this type o
On sexta-feira, 6 de julho de 2012 15.06.34, Tr3wory wrote:
> On Fri, Jul 6, 2012 at 2:42 PM, Richard Moore wrote:
> > On 6 July 2012 13:26, Tr3wory wrote:
> >> But the QWidget's weight property doesn't have a corresponding
> >> weightChanged() signal (nor sizeChanged() or something higher level)
On Fri, Jul 6, 2012 at 2:42 PM, Richard Moore wrote:
> On 6 July 2012 13:26, Tr3wory wrote:
>> But the QWidget's weight property doesn't have a corresponding
>> weightChanged() signal (nor sizeChanged() or something higher level).
>> Actually it doesn't have any NOTIFY signal at all.
>>
>
> QWidg
On 6 July 2012 13:26, Tr3wory wrote:
> But the QWidget's weight property doesn't have a corresponding
> weightChanged() signal (nor sizeChanged() or something higher level).
> Actually it doesn't have any NOTIFY signal at all.
>
QWidget doesn't have a weight() property. If it's something you've
a
Look at the QNetworkRequest and QNetworkReply classes, particularly the
header() and rawHeader() functions of QNetworkReply
These APIs are also available in 4.6, 4.7, 4.8.
Please write your code to use this API if at all possible, since it is still
getting support.
Those deprecated classes have
On Fri, Jul 6, 2012 at 1:56 PM, André Somers wrote:
> Op 6-7-2012 13:30, Olivier Goffart schreef:
>> On Friday 06 July 2012 13:02:16 André Somers wrote:
>> As already pointed out, adding NOTIFY signal is not binary incompatible. Feel
>> free to submit patches that add them :-)
Ok, I may misremembe
Op 6-7-2012 13:30, Olivier Goffart schreef:
> On Friday 06 July 2012 13:02:16 André Somers wrote:
>> Op 6-7-2012 12:45, Tr3wory schreef:
>>> Hi all!
>>>
>>> I found the QML's property binding system really powerful, but as far
>>> as I understand on the C++ side it relies on the property's NOTIFY
>
On Friday 06 July 2012 13:02:16 André Somers wrote:
> Op 6-7-2012 12:45, Tr3wory schreef:
> > Hi all!
> >
> > I found the QML's property binding system really powerful, but as far
> > as I understand on the C++ side it relies on the property's NOTIFY
> > signal.
> > I know the notify signal is add
On sexta-feira, 6 de julho de 2012 17.08.08, Alan Alpert wrote:
> > Most c++ developers wouldn't want to choose between stability and
> > performance.
> > I'm adventurous, just point me at the "qt private header forum" where
> > interface changes are community-driven and I'll sign up.
> > I'll unde
On 6 July 2012 11:45, Tr3wory wrote:
> I know the notify signal is added around Qt 4.6, and as far as I
> understand we couldn't add more signals to existing properties in the
> 4.x timeframe because of the binary compatibility. (Please correct me
> if I'm wrong about this.)
This is wrong, you ca
Op 6-7-2012 12:45, Tr3wory schreef:
> Hi all!
>
> I found the QML's property binding system really powerful, but as far
> as I understand on the C++ side it relies on the property's NOTIFY
> signal.
> I know the notify signal is added around Qt 4.6, and as far as I
> understand we couldn't add more
Hi all!
I found the QML's property binding system really powerful, but as far
as I understand on the C++ side it relies on the property's NOTIFY
signal.
I know the notify signal is added around Qt 4.6, and as far as I
understand we couldn't add more signals to existing properties in the
4.x timefr
> I don't see a problem with a QPoint3D and QPointF3D class in QtCore, in
> Qt 5.1, provided you also fix any ambiguities with QVector3D's existence.
Okay, I will try to put up something soon with WIP then, based
somewhat on the current QPoint(F) implementations. I will also double
check the Qwt n
I just create a bug report, and hope someone can take of.
It's only Qt5 issue, Qt4 works well!!
2012/7/5 Loaden
> Yes, same problem happened when using qmake.
> for qbs, I made a patch for link to static library, see:
> https://codereview.qt-project.org/#change,29232
>
> 2012/7/5
>
> Does the
Hi All,
> Do you have the feeling that something is missing?
In principle, everything is ready, except for the small things:
1. While not working full installation Debug and Release versions for Windows
(until can only install by separately). Need help of it implementation.
2. To the documentat
On Fri, 6 Jul 2012 07:23:11 ext Philip Ashmore wrote:
> On 06/07/12 02:51, Alan Alpert wrote:
> > On Fri, 6 Jul 2012 02:32:06 ext Philip Ashmore wrote:
> >> ...
> >> Qt itself is IMHO strugging with the divide between
> >>
> >> closed source == api stability but dates badly
> >> open sou
On Fri, Jul 6, 2012 at 8:23 AM, Philip Ashmore
wrote:
> Good point. I googled "using qt private headers" - not very useful.
> Could you post a link?
Probably because it's more or less new to Qt 5.
QT += core core-private
.. and you may now use both public and private headers from QtCore.
The sa
32 matches
Mail list logo
