At risk of seeming like all we do is agree with each other, I have to
say I agree with Will regarding the goal of representing what is on the
screen in a way that photon and non-photon dependent people can
collaborate. I'm also wondering if my suggestion (of a list of tables)
might be confusing wh
Hi Mike:
As was suggested by Li Yuan, the first view looks a lot like one of the
gtk-demo demos. In particular, the "Tree View"->"Tree Store" demo:
http://master.gnome.org/~wwalker/Screenshot-CardPlanningSheet.png
In accerciser, this shows up as a "tree table" with a very flat
hierarchy. T
I would wind up having to create/destroy atk objects anyway since the size of
the tables would usually change, as would the UIA providers that are exposed.
It is also possible to disable groups, and there is another view which acts
like a listbox.
Anyway, I'm realizing that the Details view is
Hi Mike,
For both views I think I would prefer them exposed as a list of 2
ATK_ROLE_TABLE controls and the group names might simply be
accessible-table-caption properties (unless they are user-actionable).
This way you might actually get away with not having to destroy/create
any atk objects when
Hi all,
I am trying to map the MWF ListView control to atk (via UI automation).
I don't believe there is a gtk control equivalent to it, and I want our
code to work well with Orca for instance, so I wanted to ask if anyone
wanted to give input as to what I should do to map it. It has several
