Re: [g-a-devel] ATK API addition + deprecation

[Piñeiro <apinheiro igalia com>]

From: Fernando Herrera <fherrera onirica com>

> Rationale: the current "text-changed" signal (that includes
> text-changed::insert and text-changed::delete)  in Atk includes only
> the offset and the length of the text insert/removed. The mapped
> at-spi event includes the inserted/deleted text, so the bridge needs
> to get that text. For atk implementations that fires the event async
> (like Gecko 2.0 of Java) the actual text has been already changed when
> the bridge queries that text.

And in the case of sync events, you need to be really careful, and
emit the events in the proper moment, that can be different on the
insert and on the delete, so the AT tool could obtain the proper text
inserted or deleted. This add confusion to the code and IMHO, it is
error prone.

> Proposal: Add 3 new signals "text-insert", "text-remove" and
> "text-update" including offset, lenght and text params. We would mark
> as deprecated the old "text-changed" signal.

Could you ellaborate this "text-update"? With the current wisdom,
AFAIK, if you update a text, is the same that emit a remove and a
insert signal.

BR

[1] http://bugzilla.openedhand.com/show_bug.cgi?id=1841
[2] http://bugzilla.openedhand.com/show_bug.cgi?id=1894

===
API (apinheiro igalia com)