Make it easier to select a custom proxy object with a class name different from the QML type

Bug #1337004 reported by Leo Arias
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Autopilot
Fix Committed
Undecided
Christopher Lee

Bug Description

Since bug #1210260 was fixed, custom proxy objects can now extend the classmethod validate_dbus_object in order to overwrite the QML types that it matches.

However it's still hard to get it right. I keep getting other objects matching the validation, and in order to make it work I can't pass the class as the first parameter of select_single.

This should be easier and clearer. Lets say that I have many QML types 'ItemPage', each one with a different object name. If I want to make a different custom proxy object for each one, I should be able to do:

main_view.select_single(TestPage1, objectName='page1')

main_view.select_single(TestPage2, objectName='page2')

where TestPage1 and TestPage2 are not on the QML tree.

Tags: elopio

Related branches

Changed in autopilot:
assignee: nobody → Christopher Lee (veebers)
Changed in autopilot:
status: New → In Progress
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:autopilot at revision 567, scheduled for release in autopilot, milestone 1.4

Changed in autopilot:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.