[g-a-devel]gail frame bug ...

[Michael Meeks <michael ximian com>]

Hi Bill,

	At-poke is being somewhat crippled by some oddness in gailframe ( I
think ); at least, the following code:

static void
validate_up_down_linkage (Accessible *accessible)
{
        Accessible *child;
        Accessible *parent;

        child = Accessible_getChildAtIndex (accessible, 0);
        if (!child)
                return;

        parent = Accessible_getParent (child);

        g_assert (parent == accessible);
}

	when run on a 'Frame' fails - ie. the tree is broken. at-poke can
tolerate applications not having parents that are the desktop - although
that too is broken; but it can't tolerate this sort of breakage.

	WHy do we have both a Frame and a Window role ? what is the difference
and when do we use one instead of the other ? there are several
AtkObject methods a Window overrides that a Frame does not - why is that
? particularly get_parent and get_index_in_parent.

	Why does GailFrame not inherit from GailWindow or VV. ? surely this
code is shared ? Why does GailWindow use 'gpointer parent_class' instead
of using the most commonly chained to base class type, such as
AtkObjectClass to avoid unneccessary casts ?

	Regards,

		Michael.

-- 
 mmeeks gnu org  <><, Pseudo Engineer, itinerant idiot