RE: [g-a-devel] AtkInterfaces for gnome-about
- From: "Mukund" <mukund rajagopalan wipro com>
- To: "'Padraig O'Briain'" <Padraig Obriain sun com>, <gnome-accessibility-devel gnome org>
- Subject: RE: [g-a-devel] AtkInterfaces for gnome-about
- Date: Mon, 18 Feb 2002 16:11:31 +0530
Padraig,
>
> I have spent some time figuring out why I could not
> manipulate gnome-about using
> the keyboard. I have logged bug 71832 and proposed a patch.
>
I too agree on doing away with the glittering stuff (sparkles:)
>
> The AT would get to the atk object by traversing the tree of
> accessible objects.
> One would call atk_object_accessible_child() on its parent.
> This will cause
> gail_container_ref_child() to be called which calls
> gtk-widget_get_accessible().
> If gtk_widget_get_accessible() returns the correct type of
> object, see above,
> then things should work.
>
Should an AT traverse the whole tree (starting from root) and cache the
entire (ATK) info about the app? I would assume that the atk object
would be created only if it's required by the AT (like for e.g., create
atk object only when the focus moves to a widget via mouse/keyboard).
Can you please clarify on this?
Cheers,
Mukund.
begin 666 Wipro_Disclaimer.txt
M*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BI$:7-C;&%I;65R*BHJ*BHJ*BHJ
M*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ"B @(" @( T*#0H-"DEN9F]R
M;6%T:6]N(&-O;G1A:6YE9"!I;B!T:&ES($4M34%)3"!B96EN9R!P<F]P<FEE
M=&%R>2!T;R!7:7!R;R!,:6UI=&5D#0II<R G<')I=FEL96=E9"<@86YD("=C
M;VYF:61E;G1I86PG(&%N9"!I;G1E;F1E9"!F;W(@=7-E(&]N;'D 8GD@=&AE
M#0II;F1I=FED=6%L(&]R(&5N=&ET>2!T;R!W:&EC:"!I="!I<R!A9&1R97-S
M960N(%EO=2!A<F4@;F]T:69I960 =&AA="!A;GD-"G5S92P 8V]P>6EN9R!O
M<B!D:7-S96UI;F%T:6]N(&]F('1H92!I;F9O<FUA=&EO;B!C;VYT86EN960@
M:6X =&AE($4M34%)3 T*:6X 86YY(&UA;FYE<B!W:&%T<V]E=F5R(&ES('-T
M<FEC=&QY('!R;VAI8FET960N"@T*#0H-"B J*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ
M*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ*BHJ
&*BHJ* T*
end
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]