Re: [g-a-devel] Do we really need 'press' and 'release' AtkAction types in addition to 'click'?

[Peter Korn <peter korn oracle com>]

Joanie,

"pressed" should be equivalent to a mouse-down-but-not-released, which often triggers visual feedback from the widget.  At least for programmatic testing, this may be useful to test for.  I don't have an immediate accessibility use case to hand...


Peter

On 6/20/2011 1:07 PM, Joanmarie Diggs wrote:

Hi Nagappan.

Example: Selecting multiple files in nautilus:
* press shift key
* select multiple file with mouse click
* release shift key

I should have specified button (i.e. the widget) in the subject. My bad
for only mentioning it in the body.

Pressing and releasing keys is different. 
 

In VMware we use this for drag and drop (files) testing between host
and guest using LDTP.

You cannot drag and drop buttons, right?

--joanie

On Mon, Jun 20, 2011 at 12:52 PM, Joanmarie Diggs <joanied gnome org>
wrote:
        Hey guys.
        
        Benjamin asked why we need 'press' and 'release' AtkAction
        types in
        addition to 'click' for buttons. I think it's an excellent
        question. Do
        we really need all three, or is 'click' all that's needed?
        
        I'm good with just 'click'. Others?
        
        --joanie
        
        _______________________________________________
        gnome-accessibility-devel mailing list
        gnome-accessibility-devel gnome org
        http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel



-- 
Linux Desktop (GUI Application) Testing Project -
http://ldtp.freedesktop.org
http://nagappanal.blogspot.com

_______________________________________________
gnome-accessibility-devel mailing list
gnome-accessibility-devel gnome org
http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel

--

Peter Korn | Accessibility Principal
Phone: +1 650 5069522
500 Oracle Parkway | Redwood City, CA 94065
Oracle is committed to developing practices and products that help protect the environment