Re: [g-a-devel]Re: text_attributes_changed

[Bill Haneman <bill haneman sun com>]

On Thu, 2003-02-13 at 09:20, Padraig O'Briain wrote:
> I have not found where we currently use this signal.
> 
> It sounds correct that we should report the range over which attributes are 
> changed but I would like to have a concrete example of where attributes are 
> changed.

Since we currently report 'selected' as a text attribute, it's possible
that for consistency we want to emit this signal as selections are
made.  But that particular case is redundant with
text-selection-changed, so I am unconvinced.

Our standard little demo apps aren't allowing us to do styled text, etc;
do we have a gtk2 app that allows the user to style text available? 
That would be a concrete example.

Mozilla certainly should emit this in a lot of places but Moz will want
a gtk+ example to look at.  Who has a tiny application/applet that
allows, say, boldfacing of text?

-Bill

> 
> Padraig
> 
> > Subject: text_attributes_changed
> > To: "Padraig O'Briain" <Padraig Obriain sun com>
> > Cc: gnome-accessibility-devel gnome org
> > Mime-Version: 1.0
> > Content-Transfer-Encoding: 7bit
> > 
> > Looking at atktext.c, it looks as though this event doesn't marshal any
> > range/offset data.
> > 
> > That seems wrong to me, since you'd want to know the range over which
> > text attributes changed.
> > 
> > Do we need to deprecate this event and replace it with
> > text_attribute_range_changed or something? Or am I misreading the ATK
> > signal declaration?
> > 
> > -Bill
> > 
> > -- 
> > Bill Haneman <bill haneman sun com>
> > 
> 
> _______________________________________________
> Gnome-accessibility-devel mailing list
> Gnome-accessibility-devel gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
-- 
Bill Haneman <bill haneman sun com>