[g-a-devel]hidden or sensitive state

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

Michael,

Thanks for finding these issues.

I will deal with them in separate mail messages.

I assume by 'hidden' you mean a GtkWidget for which GTK_VISIBLE is not set.

Currently, the way we handle this is by not setting the state ATK_STATE_VISIBLE.

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.

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?

Padraig

> Subject: misc. bugs ...
> 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 there,
> 
> 	Sorry to spam the list, but bugzilla is totally broken for me, won't
> respond correctly, so here goes [ there are several here ]:
> 
> 	* Atk seems to not honour the 'hidden' state - it is vital that
> 	  this is done, since programmers rely on eg. 'clicked' not
> 	  being activated on hidden widgets - fatal crasher bugs all
> 	  over. This can be seen in an at-poke at nautilus the desktop
> 	  window shows a menu that isn't there.
>