Expose GtkBuilder widget identifiers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
autopilot-gtk |
Fix Released
|
High
|
Martin Pitt | ||
autopilot-gtk (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I'm trying to write some tests for evince or gedit for evalutating autopilot with GTK. I currently find it really hard to test the expected state as the widget tree is not very easy to traverse (see also bug 1082388 and bug 1082385).
The objects on the application widget tree should have proper identifiers that are given to them in the GtkBuilder .ui files. These identifiers are the ones that the actual program code uses to refer to them, so they are both stable, and also the most appropriate means to identify a particular widget.
I know that GTK currently does not seem to expose the GtkBuilder IDs to the widgets, so we might need to fix that (and add a GTK+ task). It might be possible to access them at the C level though, in the autobuilder GTK module?
Related branches
- PS Jenkins bot: Approve (continuous-integration)
- Thomi Richards (community): Approve
-
Diff: 126 lines (+36/-27)3 files modifiedlib/GtkNode.cpp (+9/-0)
tests/autopilot/tests/test_actions.py (+4/-18)
tests/autopilot/tests/test_properties.py (+23/-9)
Changed in autopilot: | |
assignee: | Thomi Richards (thomir) → nobody |
no longer affects: | autopilot |
Changed in autopilot-gtk: | |
importance: | Undecided → High |
tags: | added: patch |
Changed in autopilot-gtk: | |
status: | Fix Committed → Fix Released |
This sounds like an issue in autopilot-gtk to me. I've assigned Allan Lesage to look into this - hopefully between the three of us we can work this out.
Cheers,