After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 537954 - No valid equality check for nodes
No valid equality check for nodes
Status: RESOLVED FIXED
Product: dogtail
Classification: Deprecated
Component: Framework
CVS HEAD
Other Linux
: Normal normal
: ---
Assigned To: Dogtail Maintainers
Dogtail Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-12 09:31 UTC by Yann Dirson
Modified: 2008-06-13 14:35 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Yann Dirson 2008-06-12 09:31:19 UTC
If I walk down the tree and memorize a well-identified set of nodes, and later try to compare the results of a findChildren() call to those well-known nodes, I realize they do not match, despite .blink() really showing the same (text entry) widget:

- the objects do not have the same id(), which is surprising in itself, showing that there is a waste of RAM by object duplication, so 'a is b' does not work
- 'a == b' does not work either

Maybe __cmp__ could be implemented for Node objects, so at least 'a == b' can be used, but it would seem much better to me to avoid the duplication of objects in RAM (although that might be an issue in python-atspi or even in atk).

Even if fixing an underlying lib is the best long-term solution, it may be useful to implement __cmp__ so dogtail can work with any version of the to-be-fixed lib.
Comment 1 Zack Cerza 2008-06-13 14:35:15 UTC
The equality check should be implemented and working just fine in SVN. Please reopen if this is not the case.