dogtail-devel [Bug 321625] New: Better debug names for search results in procedural.py
- From: "dogtail (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
- To: dogtail-devel-list gnome org
- Subject: dogtail-devel [Bug 321625] New: Better debug names for search results in procedural.py
- Date: Wed, 16 Nov 2005 12:01:42 -0500 (EST)
Do not reply to this via email (we are currently unable to handle email
responses and they get discarded). You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=321625
dogtail | Framework | Ver: CVS HEAD
Summary: Better debug names for search results in procedural.py
Product: dogtail
Version: CVS HEAD
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: Framework
AssignedTo: dogtail-maint gnome bugs
ReportedBy: dmalcolm redhat com
QAContact: dogtail-maint gnome bugs
CC: all-bugs bugzilla gnome org
Nodes have a debugName attribute which is set up by a search, by calling a
method on the Predicate class. This gives nice readable debug names for the nodes
e.g.
"File" menu
"Cancel" button
etc
All of the searches in procedural.py seem to be ultimately doing a search using
a GenericPredicate. This gives you a very generic debug name for the result node
e.g.
name="File" roleName="menu"
name="Cancel" roleName="button"
I think the former style of debug names are much better, and it would be good to
get this supported throughout the procedural.py API. This could be done by
either using more specific Predicate subclasses, or by simply overwriting the
Node.debugName variable (I'd greatly prefer the former approach since it
leverages lots of existing code e.g. handling i18n)
------- You are receiving this mail because: -------
You are watching the assignee for the bug.
You are watching the QA contact.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]