Re: gtk_entry and "changed" signal in gtk+-2.0

[Owen Taylor <otaylor redhat com>]

Oliver Rauch <oliver rauch rauch-domain de> writes:

> Hi.
>
> In gtk+-1.2 GtkEntry is based on GtkEditable which has a signal "changed".
>
> In gtk+-2.0 GtkEntry is based directly on GtkWidget. There is no official "changed"
> signal any more (although it is emited).
>
> Is there a defined way to get an information about any change in a GtkEntry widget
> with gtk+-2.0 ?

It's still an "official" signal, on the GtkEditable interface:

 http://developer.gnome.org/doc/API/2.0/gtk/gtk-gtkeditable.html

(The docs there are a little out of date, since GtkEditable is no longer a base
class, but an interface.)
 
> My problem is the following:
> When I use my gtk+-1.2 source for gtk+-2.0 and try to use the "changed" signal,
> this in general works, but when gtk_entry_set_text() is called then the
> "changed" signal is emited twice.
> In the callback that is called when the first of this two "changed" signals is
> emited the function gtk_entry_get_text does not return the proper text.

 http://bugzilla.gnome.org/show_bug.cgi?id=64998

[ What if the user deleted the text and typed something else in? I don't think
  it should be a huge problem for most apps if the contents of an entry are
  temporarily in an empty state. ]

Regards,
                                        owen