Re: [g-a-devel] API deprecations?

[Bill Haneman <Bill Haneman Sun COM>]

Aaron Leventhal wrote:
> So is armed after the mousedown on a button but before the mouse up?
> I wonder what happens if you click and drag. In Gnome, Firefox and 
> other apps I've seen, if you click-drag on a button it just focuses 
> the button but does not activate it because the mouse up occurs 
> somewhere else. There's no way to know ahead of time.
>
> Incidentally, when a mouse down does occur on a button that's when 
> focus happens. So watching mouse down via system events and focus 
> events to buttons may be an alterative way to get the same information.
Not sure it is - in Java and, I think, gtk+, the behavior is different 
from what you describe for Firefox.  Perhaps firefox buttons should 
never expose this state.

Bill
> - Aaron
>
>
> Bill Haneman wrote:
> > Aaron Leventhal wrote:
> >  
> > > Hi Bill,
> > >
> > > Thank you -- this helps IMO. Couple of questions:
> > >
> > > * What is the potential use case for STATE_ARMED?
> > >     
> >
> > There are probably lots of them, though they might not be terribly 
> > common.
> >
> > At present STATE_ARMED is the only way to know that a 
> > widget/button/thing is
> > "pressed and will be invoked when the mouse button is released".  An 
> > AT which either monitors the mouse or which synthesizes mouse events 
> > might need to know that, and possibly a talking interface would even 
> > let the user know about it.  It could also potentially be useful to 
> > OSKs or test tools since the information does tell you something 
> > about the state of the interface; if you're doing things async you 
> > might need to wait for the state to change to/from ARMED before doing 
> > something else.
> >
> > Bill
> >
> > _______________________________________________
> > Gnome-accessibility-devel mailing list
> > Gnome-accessibility-devel gnome org
> > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
> >
> >