On Friday, 6 de January de 2012 12.26.32, aaron.kenn...@nokia.com wrote:
> Hi,
>
> Nice catch. I've added http://codereview.qt-project.org/12392 - feel free
> to review if you're not beaten to it :)
Thanks for being quick about this likely-to-be-P5-bug :-)
Unfortunately, the code is beyond me.
Hi,
Nice catch. I've added http://codereview.qt-project.org/12392 - feel free to
review if you're not beaten to it :)
Cheers,
Aaron
On 06/01/2012, at 1:01 AM, ext Thiago Macieira wrote:
> On Wednesday, 4 de January de 2012 16.05.36, aaron.kenn...@nokia.com wrote:
>> We don't allow signal or
On Wednesday, 4 de January de 2012 16.05.36, aaron.kenn...@nokia.com wrote:
> We don't allow signal or property names to start with an uppercase letter
By the way, the caret should point to the uppercase letter, not to "property",
in:
file:///tmp/foo.qml:4:5: Property names cannot begin with an u
Hi,
On 04/01/2012, at 3:29 PM, ext Thiago Macieira wrote:
> On Wednesday, 4 de January de 2012 09.42.52, Atlant Schmidt wrote:
>> Let me more-explicitly/completely state the rule
>> that I use:
>>
>>1. Always use the canonical casing for an identifier.
>>
>>2. Don't create any other i
On Wednesday, 4 de January de 2012 09.42.52, Atlant Schmidt wrote:
> Let me more-explicitly/completely state the rule
> that I use:
>
> 1. Always use the canonical casing for an identifier.
>
> 2. Don't create any other identifiers that differ
>from an existing canonical identif
pment] Possible bug in signals and slots handling in QML.
On Wednesday, 4 de January de 2012 07.51.48, Atlant Schmidt wrote:
> Thiago, et al.:
>
> This is another one of those "don't play in the
> grey areas of the language" things.
>
> Even if iden
On Wednesday, 4 de January de 2012 07.51.48, Atlant Schmidt wrote:
> Thiago, et al.:
>
> This is another one of those "don't play in the
> grey areas of the language" things.
>
> Even if identifiers are case-sensitive, one should
> probably never depend upon that; why tempt fate?
"You shou
lopment-bounces+aschmidt=dekaresearch@qt-project.org
[mailto:development-bounces+aschmidt=dekaresearch@qt-project.org] On Behalf
Of Thiago Macieira
Sent: Wednesday, January 04, 2012 06:58
To: development@qt-project.org
Subject: Re: [Development] Possible bug in signals and slots handl
On Wednesday, 4 de January de 2012 06.32.52, martin.jo...@nokia.com wrote:
> 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
> n
@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
sday, January 03, 2012 8:25 PM
> To: development@qt-project.org
> Subject: [Development] Possible bug in signals and slots handling in QML.
>
> Hi,
>
> in a recent conversation on QtDN, we have identified a possible bug in QML
> (Qt Quick 1, that is. It's possible t
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
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
14 matches
Mail list logo
