Autopilot Qt Support

Value of MouseArea.enabled property always incorrectly reported as True

Bug #1170764 reported by Olivier Tilloy on 2013-04-19

This bug affects 1 person

	Status	Importance	Assigned to
Autopilot Qt Support	Fix Released	Undecided	Olivier Tilloy
autopilot-qt (Ubuntu)	Fix Released	Undecided	Unassigned
Raring	Won't Fix	Undecided	Unassigned

Bug Description

Steps to reproduce:
1) Run the attached QML example in qmlscene, with the '-testability' command line argument:
qmlscene test.qml -testability
2) Run the autopilot GUI: autopilot vis
3) In the autopilot GUI, select QtQmlViewer, and select the QQuickMouseArea in the hierarchy of objects
4) Inspect the value of the 'enabled' property

Expected result: autopilot reports False
Current result: autopilot reports True

Related branches

lp:~osomon/autopilot-qt/do-not-override-properties

Merged into lp:autopilot-qt at revision 54

Michael Zanetti (community): Approve on 2013-04-30

PS Jenkins bot: Approve (continuous-integration) on 2013-04-30

lp:ubuntu/saucy-proposed/autopilot-qt

Revision history for this message

Olivier Tilloy (osomon) wrote on 2013-04-19:

test.qml Edit (53 bytes, text/plain)

Revision history for this message

Olivier Tilloy (osomon) wrote on 2013-04-29:

I suspect that this has to do with the fact that MouseArea inherits from Item, and it overrides the 'enabled' property.
Could it be that the introspection incorrectly gets the parent property? Or that it gets both properties, but only one is exposed in autopilot?

Olivier Tilloy (osomon) on 2013-04-29

affects:

autopilot → autopilot-qt

Olivier Tilloy (osomon) on 2013-04-30

Changed in autopilot-qt:
assignee:	nobody → Olivier Tilloy (osomon)
status:	New → In Progress

Revision history for this message

PS Jenkins bot (ps-jenkins) wrote on 2013-04-30:

Fix committed into lp:autopilot-qt at revision 54, scheduled for release in autopilot-qt, milestone Unknown

Changed in autopilot-qt:
status:	In Progress → Fix Committed

Olivier Tilloy (osomon) on 2013-05-14

Changed in autopilot-qt:
status:	Fix Committed → Fix Released

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-06-07:

This bug was fixed in the package autopilot-qt - 1.3daily13.06.05-0ubuntu1

---------------
autopilot-qt (1.3daily13.06.05-0ubuntu1) saucy; urgency=low

  [ Michael Zanetti ]
  * update tests to work with AP 1.3.
  * make it work with Qt 5.0.2.

  [ Christopher Lee ]
  * Adding GetVersion so we can check that the version of the DBus
    protocol is as expected.

  [ Olivier Tilloy ]
  * Do not override an existing property with the value of a parent
    object. (LP: #1170764)

[ Ubuntu daily release ]
* Automatic snapshot from revision 61

autopilot-qt (1.3daily13.05.24ubuntu.unity.next-0ubuntu1) raring; urgency=low

  [ Michael Zanetti ]
  * update tests to work with AP 1.3.
  * make it work with Qt 5.0.2.

[ Ubuntu daily release ]
* Automatic snapshot from revision 60 (ubuntu-unity/next)

autopilot-qt (1.3daily13.05.09ubuntu.unity.next-0ubuntu1) raring; urgency=low

  [ Mathieu Trudel-Lapierre ]
  * debian/control: don't build the binary packages on powerpc; also remove
    armel from the list since we don't build for it anymore.

[ Ubuntu daily release ]
* Automatic snapshot from revision 57 (ubuntu-unity/next)

autopilot-qt (1.3daily13.05.03ubuntu.unity.next-0ubuntu1) raring; urgency=low

[ Christopher Lee ]
* Bump version number

[ Michael Zanetti ]
* [FFE] autopilot-qt lacks testing (LP: #1157697)

[ Thomi Richards <email address hidden>, Christopher Lee ]
* DBus wire protocol changes required (LP: #1155351)

[ Thomi Richards ]
* DBus wire protocol changes required (LP: #1155351)

  [ Olivier Tilloy ]
  * Value of MouseArea.enabled property always incorrectly reported as
    True (LP: #1170764)

[ Ubuntu daily release ]
* Automatic snapshot from revision 54 (ubuntu-unity/next)
-- Ubuntu daily release <email address hidden> Wed, 05 Jun 2013 07:08:47 +0000