[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Some thoughts on kdelibs et al.
From:       Richard Moore <rich () ipso-facto ! freeserve ! co ! uk>
Date:       2001-09-25 16:33:35
[Download RAW message or body]



Andrew Sutton wrote:
> 
> On Tuesday 25 September 2001 10:53, John Gluck wrote:
> > Hi
> >
> > To see which if any virtual methods are added by the class you need only
> > look at the immediate predecessor which is fairly trival.
> > On the other hand, if you need to go down (up) a hierarchy a half dozen
> > levels or so each time you want to find out if a method is virtual that can
> > get very tedious.
> > Also, most classes I've seen don't add new virtuals. There are probably
> > exceptions but...
> 
> actually, since we're on the subject of accessors and attributes, etc..
> 
> why not just use Qt's built in property stuff. it lets you define the
> protection of attributes (i think) and automatically creates accessors and
> mutators for you... it also registers those properties with that object's
> meta-data class (an added bonus).

This is wrong, it doesn't work like that. The QProperty stuff simply
gives you a way to access the existing accessors at run time. Please
don't confuse the issue even more...

Rich.



> 
> i'm not really sure how it works, if all the property members are created
> private however.
> 
> i know it has some drawbacks however - i don't think you can actually
> specifiy the function signature or the implementation for more complicated
> accessors or mutators (i could be wrong).
> 
> andy
> 
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]