Re: [g-a-devel]gnopernicus should read new name when received "accessible-name" changed signal

[Bill Haneman <bill haneman sun com>]

Thanks Bolian.  Your suggestion that property-change:accessible-name
should be sent, and listened for, seems correct to me.

However, for the actual scenario that led you to log this bug, we
probably need to do more thinking.  Under what conditions should such a
change be expected, and when should an AT present the new information? 
It may be impractical to expect gnopernicus, for instance, to *always*
speak accessible-name changes, particularly for widgets that aren't the
currently focussed accessible, since a name-change by itself doesn't
convey enough context information for a screenreader to make a good
presentation.  Is there perhaps another way to present this information
which is more 'general', i.e. should the information really be in a
ROLE_STATUS_BAR object which is generating text-changes, etc. etc.

So I think we should discuss the specific use case here since widgets
"changing names" at runtime are not a commonplace occurrence.

- Bill


 Wed, 2003-08-27 at 03:20, Bolian Yin wrote:

Bill Haneman wrote:

    Your bug report doesn't have any description.  Could you please include
    a detailed description and justification?
Sorry for that.  I have added description in the bug report:


------- Additional Comments From Bolian Yin 2003-08-26 22:12 -------


Sorry for the incomplete report.

I mean when the accessible-name changed (e.g. by atk_object_set_name),
"property-change:accessible-name" signal will be sent out. Gnoperniucs
should listen on that and report the new name of the widget.

-Bolian