@Gregory: already tried using an id - doesn't work, it will call ItemB.foo
(causing an infinite loop in this case)
@aaron: Thanks for clarifying this. Would be great to have that supported in
future versions though, it's a pretty standard OO feature nowadays :)
I've worked around this by defining functions with separate names in the
base item, but it quickly gets tiresome in a larger hierarchy. Here is how
it can be done:
<ItemA.qml>
Item {
funciton fooA() {
console.log("fooA");
}
function foo() {
fooA();
}
}
<ItemB.qml>
ItemA {
function fooB() {
console.log("fooB");
fooA();
}
function foo() {
fooB();
}
}
_______________________________________________
Qt-qml mailing list
[email protected]
http://lists.qt.nokia.com/mailman/listinfo/qt-qml
