Buttons and AtkValue
- From: "Padraig O'Briain" <Padraig Obriain Sun COM>
- To: gnome-accessibility-list gnome org
- Subject: Buttons and AtkValue
- Date: Thu, 26 Apr 2001 11:26:58 +0100 (BST)
My excuse here is that I am following Java. AccessibleAbstractButton implements
AccessibleValue to set a button to be selected (or not) and get the selected
state. I propose to follow the same convention for ATK.
My understanding is that "selected" is equivalent to "checked". I think I lied
in my previous statement about not having an action "toggle". A button has one
action which is to click the button which is probably the same as toggle.
Padraig
>
>
> >GtkToggleButton Notes:
> >The comments on GtkButton and AtkAction interface also apply here; i.e. one
action on a button. I have
> >GaelToggleButton implementing AtkValue interface to set the button to
> >active or
> >not so I do not have an action "toggle".
> >
> >***
> My understanding of AtkValue is that it is for things which can have a
> range of values, and that the "checked" state is for objects which only
> have two states.
> ***
>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]