[g-a-devel]Re: gnopernicus question: why only report selection on combox.

[remus draica <rd baum ro>]

Hi Bill,

Please read my comments.

Regards,
Remus

On Tuesday 09 September 2003 15:23, Bill Haneman wrote:
> On Tue, 2003-09-09 at 13:07, remus draica wrote:
> > Hi,
> >
> > Because in other cases this event is followed by a focus: event. In case
> > of menus after a selection-changed event for the menu a focus: event for
> > new focused item will came. So, gnopernicus is interested by this event
> > only in case of combos.
>
> Remus:
>
> I don't think you can or should count on this behavior.  Recall that we
> DO NOT guarantee even the order of event delivery, and we certainly do
> not guarantee that focus: events follow all selection-changed events.

IN NO CASE GNOPERNICUS MAKES ANY PRESUMPTION THAT EVENTS SHOULD BE IN A 
PARTICULAR ORDER.

Let say that you typed 2 characters in a text field. Then, all next events 
will be received:
	1. text-insert
	2. caret-moved
	3. text-insert
	4. caret-moved

First 2 events are fired when first char is typed and last 2 when the second 
char is typed. Event #1 and #2 can came in any order. Same observation for #3 
and #4. But in no case  ALL events can came in any order, let say #4 #2 #1 
#3. Also I think (and hope) that situation never happens because of at-spi.

>
> If you wish to ignore selection-changed events for menus only, that
> might be appropriate, but I think that it would be safer and more robust
> to ignore "focus:" events that immediately follow selection-changed
> events and which are the same as the newly-selected item.  That would be
> a more general and robust heuristic.
>

I don't think this is a good idea, because till now, in case described above 
everything works ok. If you have any STRONG argument, please let me know.

> - Bill
>
> > If you know a case in which gnopernicus is not working properly, please
> > let me know.
> >
> > Regards,
> > Remus
> >
> > On Tuesday 09 September 2003 13:54, Bolian Yin wrote:
> > > Hi,
> > >
> > > currently gnoperniucs only report "selection-changed" signal when the
> > > current focused widget is a combox, why not report it on all object
> > > that support selection interface?
> > >
> > > Thanks,
> > > Bolian
>
> _______________________________________________
> Gnome-accessibility-devel mailing list
> Gnome-accessibility-devel gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel