On Mon, Oct 22, 2012 at 10:08:14AM +0200, Samuel Rødal wrote:
> > On 19 October 2012 21:56, Oswald Buddenhagen <oswald.buddenha...@digia.com>
> > wrote:
> >> i don't see why this shouldn't apply equally to qml. if it poses a
> >> problem in a particular case, it is most likely indicative of a serious
> >> API issue.
>
> What would be indicative of a serious API issue?
>
property overloading.
either it is a different property - then you should have used
descriptive names to avoid a clash.
or it is actually an attempt to have (virtually) the same property
duplicated in the derived class. then you are really in trouble.
_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
