Re: [g-a-devel]Tree updates in at-poke



On Mon, 2003-11-17 at 09:15, padraig o'briain wrote:
> David,
> 
> The purpose of at-poke is to provide a tool to help determine whether accessibility bugs are in assistice technology, e.g. gok or gnopernicus or in the application or in the accessibility framework, i.e. at-spi, atk or gail.

>From the application developer's point of view, am I right in thinking
it's also meant as an easy test tool for checking accessibility?

> 
> at-poke should be capable of doing both "value-poking" or "value-monitoring".

Is there a UI for "value-monitoring" at the moment?  Perhaps there
should be a button that lets you open an event monitoring window for a
node in the tree (with some kind of list view showing the events as they
occur)?

Or is there a tool that does this already?  (even if it's just a cmd
line app that spews stuff out to stdout?)

> 
> If you can identify when property-change notiifcations are not being sent I can try to evaluate whether it is a bug.

I was trying to track them down using at-poke alone, and hence had some
difficulties (which motivated the patch).  

I was looking into a possible problem inside Nautilus (bug #125006),
though I believe that this _is_ sending the notifications (it was just
that the at-poke GUI wasn't updating in response to them, which had
confused me).

> 
> If you can identify when a crash occurcs and supply a back trace I can look at it.

OK.

> 
> Padraig.
> 
> Dave Malcolm wrote:
> > 
> > I've attempted to get at-poke to listen for property-change events and
> > update the left-hand pane's tree model accordingly.
> > 
> > Attached is a first pass at a patch.  I'm not convinced about it yet
> > though as:
> > (i) I'm getting occasional crashes when poking things - though these
> > might not be due to my changes.  I'm new to at-poke, and to the
> > accessibility framework, and I've not implemented a GtkTreeModel before,
> > so there might be subtleties I've missed.
> > (ii) Not everything seems to be sending property-change notifications -
> > perhaps these are bugs in the existing applications, or is this just an
> > advisory, and not mandatory?
> > (iii) Is this a good direction to take?  Is at-poke supposed to be for
> > static "value-poking", or for dynamic "value-monitoring"?
> > 
> > Thoughts?
> > 
> > --
> > David Malcolm
> > http://www.davemalcolm.demon.co.uk
> > 
> >   --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> >                          Name: tree-updates.patch
> >    tree-updates.patch    Type: text/x-patch
> >                      Encoding: 7bit
> _______________________________________________
> Gnome-accessibility-devel mailing list
> Gnome-accessibility-devel gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
-- 
David Malcolm
http://www.davemalcolm.demon.co.uk




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]