@Craig:
Good to know, thanks. To be honest, I don't think anybody actually
tried double underscores for signal name, in the conversation on QtDN
it just cropped up as a sort of "what if" scenario.
But, to take it one step further - does that really matter in QML?
MOC, AFAIK, is using signals by th
Hi,
1. The capitalization of the first alpha character after the underscore is
deliberate. Signal handlers are defined as being 'on' followed by a capital
letter. Since underscore has no capital, it must be the first non-underscore
letter.
2. on__PrivateSignal does work in Qt 5.0. We won't
>From the QtDeclarative point of view, apart from having our tests pass, I'd
>like to see some comparisons in QML load time, using photoviewer as a test
>case, for example.
Looks like performance was an important consideration in the new
implementation, but I'd like to see confirmation :-)
Br,
Hi,
I've just been trying some experimental porting of code to Qt5.
It failed because QFormBuilder is no longer available. Then I noticed that the
entire designer library and interface is no longer available.
Why was that done and can it be undone?
Thanks,
--
Stephen Kelly | Software Engi
Starting a signal name with an underscore could be viewed as a violation of the
C++ standard, depending on how you interpret it. Item 17.4.3.1.2 in the
standard reserves names beginning with an underscore as for use only by the
implementation (ie the compiler):
"17.4.3.1.2 Global names
Certain
Starting a signal name with an underscore could be viewed as a violation of the
C++ standard, depending on how you interpret it. Item 17.4.3.1.2 in the
standard reserves names beginning with an underscore as for use only by the
implementation (ie the compiler):
"17.4.3.1.2 Global names
Certain
Indeed, that looks elegant :)
Simon
--
Sent from my Nokia N903.01.12 17:46 skrev Buddenhagen Oswald (Nokia-MP/Berlin):
On Tue, Jan 03, 2012 at 01:45:27PM -0200, ext Thiago Macieira wrote:
> Configure already sets a "default" mkspec symlink that matches the target
> mkspec. Making it also create
On 1/3/12 5:45 PM, "ext Oswald Buddenhagen"
wrote:
>On Tue, Jan 03, 2012 at 01:45:27PM -0200, ext Thiago Macieira wrote:
>> Configure already sets a "default" mkspec symlink that matches the
>>target
>> mkspec. Making it also create a symlink for "default-host" which
>>matches the
>> host platf
On Tuesday, 3 de January de 2012 18.29.11, marius.storm-ol...@nokia.com wrote:
> > I solved the problem by using a special compiler, which was already
> > present in src/gui/gui.pro. qmake doesn't look into SSE2_SOURCES,
> > AVX_SOURCES, NEON_SOURCES.
>
> Right, that would work too. (as would a sep
Op 3-1-2012 21:14, Richard Moore schreef:
>>> - How many rooms, which capacity? No need to get into details but having
>>> a rough idea would be useful in order to book the right amount of space.
>>> For you this means what type of event do you want: was the event last
>>> year good or would you pr
On Tue, Jan 3, 2012 at 6:11 PM, wrote:
> On 03/01/2012 11:14, ext Quim Gil wrote:
>> After many discussions with many people we seem to agree on the following:
>>
>> - The first edition was a success and it is out of question that we need
>> to keep organizing this event in 2012.
>
> Agreed. Now
Op 3-1-2012 19:48, marius.storm-ol...@nokia.com schreef:
> On 03/01/2012 12:25, ext Jonas M. Gastal wrote:
>> On Tuesday 03 January 2012 18:11:08 marius.storm-ol...@nokia.com
>> wrote:
>>> On 03/01/2012 11:14, ext Quim Gil wrote:
- When? There have been different opinions and the trend seems t
On 03/01/2012 12:25, ext Jonas M. Gastal wrote:
> On Tuesday 03 January 2012 18:11:08 marius.storm-ol...@nokia.com
> wrote:
>> On 03/01/2012 11:14, ext Quim Gil wrote:
>>> - When? There have been different opinions and the trend seems to
>>> be that it is better to do it after Qt 5 is released, oth
On 03/01/2012 12:20, ext Thiago Macieira wrote:
> On Tuesday, 3 de January de 2012 18.16.46,
> marius.storm-ol...@nokia.com wrote:
>>> I know that because I had the exactly opposite problem Friday: I
>>> had one .cpp (qdrawhelper.cpp) that I wanted to be compiled on
>>> its own *and* as an #include
On Tuesday 03 January 2012 18:11:08 marius.storm-ol...@nokia.com wrote:
> On 03/01/2012 11:14, ext Quim Gil wrote:
> > - When? There have been different opinions and the trend seems to be
> > that it is better to do it after Qt 5 is released, otherwise people will
> > be too stuck with bugfixing an
Hi again,
I forgot on item on my list, I hope is not too late :)
A way to pause/resume the application (all QEventLoop(s)) from another thread.
It is useful because Android tries to pause the application when it goes in
background
and some time it destroys some critical resources (e.g. the Open
On Tuesday, 3 de January de 2012 18.16.46, marius.storm-ol...@nokia.com wrote:
> > I know that because I had the exactly opposite problem Friday: I had
> > one .cpp (qdrawhelper.cpp) that I wanted to be compiled on its own
> > *and* as an #include from somewhere else. qmake wouldn't do it.
>
> You
On 03/01/2012 12:01, ext Thiago Macieira wrote:
> On Tuesday, 3 de January de 2012 18.19.47, Denis Dzyubenko wrote:
>> That's the thing - it doesn't work in some cases - if you do
>> in-source-tree build of the attached project. Well now thinking
>> about it, it is probably a bug in qmake.
Sounds
On 03/01/2012 11:14, ext Quim Gil wrote:
> After many discussions with many people we seem to agree on the following:
>
> - The first edition was a success and it is out of question that we need
> to keep organizing this event in 2012.
Agreed. Now that we *are* under Open Governance, it's even mor
On Tuesday, 3 de January de 2012 18.19.47, Denis Dzyubenko wrote:
> That's the thing - it doesn't work in some cases - if you do
> in-source-tree build of the attached project. Well now thinking about
> it, it is probably a bug in qmake.
>
> Denis.
You said:
> This is because qmake decided that m
Hi,
Ok, you have caught the attention !
So, two platforms are slightly different (armv5 and armv7),
and one completely different (x86), so all this platforms must have their
own CXXFLAGS and must link to different libs.
Are you saying that all this things are possible using qmake ?
A little hel
Hi,
>> - Menus, on android the menu bar is completely different from other
> platforms
>> , it is always hidden, and to make it visible the user must press the menu
>> button. Currently there is no way to do it, because QMenuBar is a widget
> and
>> even more is part of your application w
Hi Thiago,
2012/1/3 Thiago Macieira :
> On Friday, 30 de December de 2011 14.55.55, Denis Dzyubenko wrote:
>> In qt5 modules we have exactly the same problem as in namespaced-Qt
>> itself. Hence my suggestion to solve it in the same way - I would like
>> to be able to re-use that QT_BEGIN_MOC_NAME
The Qt Contributors Summit is an event by / for the developers
subscribed to this list. Let's have here the discussion about the big
items and then we can move to the [marketing] list for the
'implementation details'.
It is urgent to book a location! Let's focus the discussion in the
points re
On Tuesday, 3 de January de 2012 16.12.11, kai.koe...@nokia.com wrote:
> PS: Was there a similar in Trolltech times, too? I'm getting old , I can't
> remember :(
No, it was different. It was the LICENSE.TROLL file's presence that triggered
the "troll build".
See:
http://websvn.kde.org/branches/qt
On Tue, Jan 03, 2012 at 01:45:27PM -0200, ext Thiago Macieira wrote:
> Configure already sets a "default" mkspec symlink that matches the target
> mkspec. Making it also create a symlink for "default-host" which matches the
> host platform would be easy.
>
> The tricky part is using that.
>
> Y
Hi,
Following change removes the -nokia-developer option from configure:
http://codereview.qt-project.org/#change,12042 . There's just no reason to
treat Nokia employees differently any more ... all it did was setting
-developer-build -commercial -confirm-license anyway.
I'm trying to clean up
On Jan 3, 2012, at 11:30 AM, ext Ville M. Vainio wrote:
> On Mon, Jan 2, 2012 at 8:20 AM, wrote:
>
>> QIcon is a style concept and belongs together with QStyle and we do not want
>> QStyle in QtGui. As both the QFileSystemModel and QStandardItemModel relies
>> on it, they cannot be moved to
On Tuesday, 3 de January de 2012 15.21.26, lars.kn...@nokia.com wrote:
> Not sure how it works currently. But in general it'd be good if we can fix
> this once and for all by adding proper cross compilation support to
> qmake/configure. Something where you can specify host vs target in the
> .pro f
CONFIG(, |) {
# Do stuff
} else {
# Do stuff
}
Might work, if you know the or mkspecs. However, for general
purpose we can introduce variables which contain these.
QMAKE_HOST_SPEC=
QMAKE_TARGET_SPEC=
for example..
--
.marius
> -Original Message-
> From: developmen
On 1/3/12 2:49 PM, "ext Kent Hansen" wrote:
>Den 01. jan. 2012 20:59, skrev ext simon.hausm...@nokia.com:
>> Whoever is going to do the work may first have to add support for host
>>builds in modules outside qtbase, in order to support v8 snapshots.
>>
>> Simon
>>
>
>Hmm, I was getting ready to c
Den 30. des. 2011 15:06, skrev ext Thiago Macieira:
> On Monday, 12 de December de 2011 19.34.21, Thiago Macieira wrote:
>> On Monday, 12 de December de 2011 18.03.53, aaron.kenn...@nokia.com wrote:
$ git reset --hard d28b6a024826aaa48a8b3e69c096d01c91aff2c9
Checking out files: 100% (894/
On Tuesday, 3 de January de 2012 14.49.41, Kent Hansen wrote:
> *tools/bootstrap*|*tools/moc*|*tools/rcc*|*tools/uic*|*linguist/lrelease*)
> SPEC=$QMAKESPEC ;;
>
> but lrelease lives in the qttools module now. So how is it built as a
> host tool when cross-compiling? Is it hard-coded somewhere else
On Tue, Jan 3, 2012 at 2:01 PM, Denis Dzyubenko wrote:
> 2011/12/29 Thiago Macieira :
>> I'd like to nominate Robin Burchell (a.k.a. w00t on IRC) for approver in Qt.
>> He's been around Qt for some time now and has been contributing both in his
>> work time and in his personal time. He was also my
2011/12/29 Thiago Macieira :
> I'd like to nominate Robin Burchell (a.k.a. w00t on IRC) for approver in Qt.
> He's been around Qt for some time now and has been contributing both in his
> work time and in his personal time. He was also my main external "sparring
> partner" when developing the Open
Den 01. jan. 2012 20:59, skrev ext simon.hausm...@nokia.com:
> Whoever is going to do the work may first have to add support for host builds
> in modules outside qtbase, in order to support v8 snapshots.
>
> Simon
>
Hmm, I was getting ready to create a JIRA task ("Add support for host
builds in
On Friday, 30 de December de 2011 14.55.55, Denis Dzyubenko wrote:
> In qt5 modules we have exactly the same problem as in namespaced-Qt
> itself. Hence my suggestion to solve it in the same way - I would like
> to be able to re-use that QT_BEGIN_MOC_NAMESPACE for qt5 modules, to
> be able to redef
On Friday 30 December 2011 14:55:55 Denis Dzyubenko wrote:
> Hi guys,
>
> With a qt5 module that we are developing, qtjsondb, we stumbled upon
> an issue with moc and our classes that are inside a namespace. Let me
> illustrate it with a code:
>
> jsondb-global.h:
>
> #if defined(QT_NAMESPACE)
>
Hi guys,
With a qt5 module that we are developing, qtjsondb, we stumbled upon
an issue with moc and our classes that are inside a namespace. Let me
illustrate it with a code:
jsondb-global.h:
#if defined(QT_NAMESPACE)
# define QT_ADDON_JSONDB_BEGIN_NAMESPACE namespace QT_NAMESPACE {
namespace Q
On Tuesday, 3 de January de 2012 09.53.41, Jonas M. Gastal wrote:
> As for removing them entirely yes, it would require changes in the HTTP
> socket engine and QAuthenticator. But given that both of them use
> QHttpResponseHeader I see no reason to duplicate the code in both classes,
> perphaps it
On Tuesday 03 January 2012 12:33:36 Peter Hartmann wrote:
> I also like first making the parts still in use private; getting rid of
> it completely is a bigger task, as it requires rewriting parts of the
> HTTP socket engine and QAuthenticator IIRC.
>
> Peter
>
> _
On 12/26/2011 11:08 AM, ext lars.kn...@nokia.com wrote:
> (...)
>> I'd say, move that class in qhttpheader_p.h
>
> Yes, let's make it private (or get rid of it if possible). For those that
> need/use QHttpHeader (and/or QHttp), we can provide the code as a small
> static library that you can includ
On 1/2/12 5:53 PM, "ext Stephen Kelly" wrote:
>On Monday, January 02, 2012 11:43:18 Olivier Goffart wrote:
>> On Monday 02 January 2012 06:20:59 gunnar.sle...@nokia.com wrote:
>> > The argument does indeed exists. QtGui's primary function is to be a
>> > windowing system and graphics enabler. T
On 12/29/11 8:48 PM, "ext Thiago Macieira"
wrote:
>
>I'm thinking the whole architecture might need to change:
>
>gcc $ make .obj/release-shared/qdrawhelper.o |& grep -c LOOP\ VECTORIZED
>112
>
>icc $ make .obj/release-shared/qdrawhelper.o |& grep -c LOOP\ WAS\
>VECTORIZED
>107
>
>This file alon
On 12/30/11 10:26 PM, "ext Thiago Macieira"
wrote:
>On Thursday, 29 de December de 2011 15.16.19, jason.bar...@nokia.com
>wrote:
>> Hi Thiago,
>>
>> > I can get started, but I need to know: how is this code tested? How
>>can I
>> > verify that things are working?
>> The best way to test this i
On 12/30/11 10:18 PM, "ext Thiago Macieira"
wrote:
>The only changes done to the file in the past almost 3 years are the
>license
>header updates and one overall change done to all draw helpers. Even the
>MMX
>helpers had two more changes in the period (one might be considered non-
>trivial).
>
+1 from me!
Cheers,
Lars
On 12/29/11 3:14 AM, "ext Thiago Macieira"
wrote:
>I'd like to nominate Robin Burchell (a.k.a. w00t on IRC) for approver in
>Qt.
>He's been around Qt for some time now and has been contributing both in
>his
>work time and in his personal time. He was also my main exte
On Mon, Jan 2, 2012 at 8:20 AM, wrote:
> QIcon is a style concept and belongs together with QStyle and we do not want
> QStyle in QtGui. As both the QFileSystemModel and QStandardItemModel relies
> on it, they cannot be moved to Gui. At least not without some surgery, and
> the surgery would
Hi,
in a recent conversation on QtDN, we have identified a possible bug in
QML (Qt Quick 1, that is. It's possible that the both issues affect
QtQuick2 too). We have also identified a confusing situation that can
be easily clarified in QDoc. First, a link to the discussion, then a
short recap on w
49 matches
Mail list logo
