It appears to have landed more than a year ago. If the problem remains in
current versions, we may want to open a new bug.
On Sat, Jan 2, 2016 at 1:06 PM, Andrew Hayzen <1269...@bugs.launchpad.net>
wrote:
> Did this fix ever land? As I am unable to access things such as the
> following in QML from autopilot.
>
> Item {
> property var currentMeta: ({})
> }
>
> --
> You received this bug notification because you are a member of Autopilot
> Hackers, which is subscribed to Autopilot Qt Support.
> https://bugs.launchpad.net/bugs/1269578
>
> Title:
> Autopilot cannot access MediaPlayer component
>
> Status in Autopilot Qt Support:
> Confirmed
> Status in autopilot-qt package in Ubuntu:
> Fix Released
>
> Bug description:
> When trying to access properties off a MediaPlayer while writing an
> autopilot test it became apparent that autopilot cannot find the
> MediaPlayer component.
>
> I have made an example application which is the SimpleUI with the
> addition of a MediaPlayer component. Within the autopilot tests it attempts
> to access the property currentIndex but fails to find the MediaPlayer with
> the following error:
> StateNotFoundError: State not found for class '*' and filters
> {'objectName': 'player'}
>
> I have linked two branches to this bug report, one being the example
> application and one being the MP for the music-app in which this issue
> was found.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/autopilot-qt/+bug/1269578/+subscriptions
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269578
Title:
Autopilot cannot access MediaPlayer component
To manage notifications about this bug go to:
https://bugs.launchpad.net/autopilot-qt/+bug/1269578/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
