Autopilot-gtk must not use memory addresses as object ids
Bug #1212926 reported by
Thomi Richards
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
autopilot-gtk |
Fix Released
|
Critical
|
Unassigned |
Bug Description
The fact that autopilot-gtk is using object memory address locations as object ids is causing problems with server-side parameter matching, where values outside MININT <-> MAXINT overflow the xpathselect rule.
Related branches
lp:~autopilot/autopilot-gtk/experimental
- PS Jenkins bot: Approve (continuous-integration)
- Martin Pitt (community): Approve
-
Diff: 957 lines (+425/-133)13 files modifieddebian/changelog (+7/-0)
debian/control (+4/-4)
debian/rules (+2/-1)
lib/GtkNode.cpp (+147/-60)
lib/GtkNode.h (+18/-8)
lib/GtkRootNode.cpp (+24/-16)
lib/GtkRootNode.h (+5/-3)
lib/Introspection.cpp (+3/-3)
lib/Variant.cpp (+168/-22)
lib/Variant.h (+3/-1)
lib/autopilot_types.h (+34/-0)
tests/autopilot/tests/test_widget_tree.py (+2/-6)
tests/autopilot/tests/test_xpath_query.py (+8/-9)
Changed in autopilot-gtk: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I don't understand that -- refreshing properties of a GObject doesn't change the address of the GObject itself. That would only happen if you destroy e. g. a button and re-create it?