[g-a-devel]Re: hidden or sensitive state
- From: Michael Meeks <michael ximian com>
- To: Padraig O'Briain <Padraig Obriain sun com>
- Cc: accessibility mailing list <gnome-accessibility-devel gnome org>
- Subject: [g-a-devel]Re: hidden or sensitive state
- Date: 19 Mar 2002 11:26:49 +0000
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.
> 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.
Hmm,
Michael.
--
mmeeks gnu org <><, Pseudo Engineer, itinerant idiot
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]