[9693] in The GTK GIMP ToolKit mailing list archive

home help back first fref pref prev next nref lref last post

[gtk-list] Re: gtk-- missing signals

daemon@ATHENA.MIT.EDU (Jan Gentsch)
Fri Oct 30 18:38:15 1998

Date: Fri, 30 Oct 1998 22:10:38 +0100
From: Jan Gentsch <gentsch@ifm.uni-hamburg.de>
To: gtk-list@redhat.com
Resent-From: gtk-list@redhat.com
Reply-To: gtk-list@redhat.com

Tero Pulkkinen wrote:

> Jan Gentsch <gentsch@ifm.uni-hamburg.de> writes:
> > I am looking at gtk+-1.1.2 and gtk---0.9.17 (Though looking at the
> > source it's the same for 0.9.19).
> > There are a number of signals defined in the gtkeditable class which are
> > not reflected in c++ interface.
> >   insert_text
> >   delete_text
> >   set_text
> > Missing this signals takes away most of the functionalty of the editable
> > class. What is the problem with these signals??
> > There are name clashes but that should be possible to circumvent??
>
> (what is this set_text() signal? My gtkeditable.c does not have it.. has
> gtkeditable.c changed recently? (my gtk+ is quite new version from cvs) :)
>

Just checked again, its propably old. It's in the documentation, but no longer
in the sources. I didn't want to complain all that much so dropped the other
signals from my list.

> I added those signals and virtual functions now, but insert_text and
> set_editable will need some thinking to do -- we would like to use
> const string& in there instead of gchar*'s.. but I'm not exactly sure
> how to implement it... :(
>
> Also, the thing I implemented now allows calling signal_emit for
> things like move_cursor, move_to_row and move_to_column etc because
> they dont have corresponding gtk_editable_move_cursor() functions.
>

Have you put it anywhere??

Jan.

-- 
To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null


home help back first fref pref prev next nref lref last post