hi, thanks for the info - this is what I needed
best regards, Ivo On 01/18/2011 03:12 PM, ext Girish Ramakrishnan wrote: > Hi, > This is a known problem - > http://bugreports.qt.nokia.com/browse/QTBUG-14089. . Fix coming in > 4.7.2 > > Girish > > On Tue, Jan 18, 2011 at 4:59 PM, Ivailo Iliev > <[email protected]> wrote: >> Hi all, >> >> I'm having case like this >> >> ItemA { >> property variant myProperty >> } >> >> ItemB { >> property alias myAlias: test.myProperty >> ItemA{ id: test } >> } >> >> And it seems that onMyAliasChanged is never fired - I need to listen to >> onMyPropertyChanged directly. But in my case I want to "hide" ItemA and >> just expose this property. >> >> Am I doing something wrong or there is another way to do it? >> >> The only thing I can think of for now is: >> >> ItemB { >> property alias myAlias: test.myProperty >> signal MyAliasHasChanged() >> ItemA >> id: test >> onMyPropertyChanged: { >> MyAliasHasChanged() >> } >> } >> } >> >> but it seems a little bit ugly and I need to use connect not only one >> alias - and it's a lot of "bogus" coding. >> >> Thanks in advance for the help, >> Ivo >> _______________________________________________ >> Qt-qml mailing list >> [email protected] >> http://lists.qt.nokia.com/mailman/listinfo/qt-qml >> _______________________________________________ Qt-qml mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-qml
