On Fri, Nov 29, 2013 at 3:03 PM, Tony Van Eerd wrote:
>>
>> On Fri, 29 Nov 2013, Tony Van Eerd wrote:
>>
>> > in the cases I am looking at, if isValid() == false, then all the
>> other
>> > properties are invalid, and return "", -1, etc. It really does mean
>> the
>> > whole object is invalid.
>>
>
> On Fri, 29 Nov 2013, Tony Van Eerd wrote:
>
> > in the cases I am looking at, if isValid() == false, then all the
> other
> > properties are invalid, and return "", -1, etc. It really does mean
> the
> > whole object is invalid.
> >
> > (except maybe an 'id', in the case of, say, a Battery o
On Fri, 29 Nov 2013, Tony Van Eerd wrote:
in the cases I am looking at, if isValid() == false, then all the other
properties are invalid, and return "", -1, etc. It really does mean the
whole object is invalid.
(except maybe an 'id', in the case of, say, a Battery object - the id
telling yo
t name per class, more context specific.
From: Hausmann Simon [mailto:simon.hausm...@digia.com]
Sent: Friday, November 29, 2013 2:20 PM
To: Tony Van Eerd; development@qt-project.org
Subject: SV: [Development] isValid() as a property
Imho isValid is fine, but generally I would suggest a mo
. november 2013
Til: development@qt-project.org
Emne: [Development] isValid() as a property
Is it common/uncommon/unheard-of to have a 'valid' property:
Q_PROPERTY( bool valid READ isValid NOTIFY validChanged )
I'm thinking about classes like 'DeviceLocation' which wou
Is it common/uncommon/unheard-of to have a 'valid' property:
Q_PROPERTY( bool valid READ isValid NOTIFY validChanged )
I'm thinking about classes like 'DeviceLocation' which would update with GPS
changes, but at some point might just become invalid (or start invalid, until
GPS turns on, etc).
