[g-a-devel]Re: hidden or sensitive state

["Padraig O'Briain" <Padraig Obriain Sun COM>]

> Subject: Re: hidden or sensitive state
> To: "Padraig O'Briain" <Padraig Obriain sun com>
> Cc: accessibility mailing list <gnome-accessibility-devel gnome org>
> Content-Transfer-Encoding: 7bit
> Mime-Version: 1.0
> 
> Hi Padraig,
> 
> On Tue, 2002-03-19 at 09:34, Padraig O'Briain wrote:
> > I assume by 'hidden' you mean a GtkWidget for which GTK_VISIBLE is not set.
> 
> 	Yes.
> 
> > Currently, the way we handle this is by not setting the state
> > ATK_STATE_VISIBLE.
> 
> 	Oh - I'm still not seeing state sets via cspi - perhaps this is the
> problem.
> 

I know Marc was working in this area. I am not sure if he has finished.

> > So, to determine when an object is visible, call
> > atk_object_ref_state_set() and then
> > atk_state_set_contains_set(state_set, ATK_STATE_SET_VISIBLE). We could
> > probably do with a function atk_object_is_visible() which does that.
> 
> 	Possibly.
> 
> > Are you are asking that the implementation of AtkAction in, e.g.
> > gailbutton.c or gailmenuitem.c should check that the widget is
> > VISIBLE and SENSITIVE before doing the action?
> 
> 	Yes - that is vital - it is an important invariant that many programs
> rely on. Is it documented somewhere that there are a load of Accessibles
> exposed that should not (and may never be) used ? a lot of widgets spend
> their lives hidden for various reasons.
> 

The fact that we have the state ATK_STATE_VISIBLE and ATK_STATE_SHOWING implies 
that not all accessible objects which are exposed will be visible on the screen.

I will update GAIL to ensure that no action is performed if the underlying 
widget is not VISIBLE and SENSITIVE.

Padraig

> 	Hmm,
> 
> 		Michael.
> 
> -- 
>  mmeeks gnu org  <><, Pseudo Engineer, itinerant idiot
>