QML types without their own properties end up with parent's type name
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Autopilot Qt Support |
New
|
Undecided
|
Unassigned |
Bug Description
Found this in the Indicators. Not sure if it's a problem with autopilot or qt.
If the subclass does not have it's own local properties the class name end's up at the first ancestor which does.
eg: (from indicators-client)
"BasicMenu.qml"
ListItem.Standard {
property bool listViewIsCurre
property QtObject menu
. . .
}
"Menu.qml"
BasicMenu {
. . .
color: "#221e1c"
HLine { ... }
HLine { ... }
. . .
}
"SwitchMenu.qml"
Menu {
id: _switchMenu
. . .
control: Switch { ... }
DBusActionState { ... }
. . .
}
self.app.
self.app.
If you add a local property to SwitchMenu (eg property alias checked : switch.checked)
self.app.
Could be something to do with the metaType className ?
description: | updated |
Yes, this is known. Thing is, that's an optimisation of the QQmlEngine itself. By the time autopilot-qt introspects the Object tree this has already happened. So not really sure if there is anything I can do. I guess the only solution would be to disable that optimisation feature in the QQmlEngine. Not sure if its worth the efforts tho. If you have and ideas how deal with this, it would be more then welcome.