On Sun, Aug 11, 2013 at 08:37:16PM +0200, Piñeiro wrote:
> On 08/09/2013 11:02 PM, Trevor Saunders wrote:
> >
> >> I think that in the end we shouldn't worry too much about this in this
> >> scope. I would maintain the temporal wrapper to the old method for this
> >> bug (fwiw, bgo#705581) and thin
Hi,
> [...]
> 2. Add a new function that will only need the offset and the
> granularity as input parameters:
>
> gchar* atk_text_get_text_for_offset (AtkText *text,
> [...]
Just to mention that after some discussion on bugzilla (see [1]), we are
thinking that perhaps a better name for this
Hi everybody,
I'm right now doing some cleaning at the documentation of atk (as a
result of doing some long-waited deprecations). As you can recall from
the atk-hackfest of 2012 [1], one of the conclusions was adding some new
signals [2] in order to deprecate AtkText::text-changed [3]. And the
si
Hi. The idea of text_update event is a substitution of
text_removed/text_inserted events pair. It's about less events and
describes better what the user does. So if the user selected the text
and typed new text then it's a case for text_update event. We never
implemented it in Firefox because AT di
