From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1732 invoked by alias); 31 Mar 2003 22:50:30 -0000 Mailing-List: contact guile-gtk-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: guile-gtk-owner@sources.redhat.com Received: (qmail 1695 invoked from network); 31 Mar 2003 22:50:28 -0000 Received: from unknown (HELO snoopy.pacific.net.au) (61.8.0.36) by sources.redhat.com with SMTP; 31 Mar 2003 22:50:28 -0000 Received: from sunny.pacific.net.au (sunny.pacific.net.au [203.2.228.40]) by snoopy.pacific.net.au (8.12.3/8.12.3/Debian-5) with ESMTP id h2VMoQvO025151 for ; Tue, 1 Apr 2003 08:50:27 +1000 Received: from wisma.pacific.net.au (wisma.pacific.net.au [210.23.129.72]) by sunny.pacific.net.au with ESMTP id h2VMoQoJ029298 for ; Tue, 1 Apr 2003 08:50:26 +1000 (EST) Received: from localhost (ppp45.dyn228.pacific.net.au [203.143.228.45]) by wisma.pacific.net.au (8.12.8/8.12.8) with ESMTP id h2VMoOqn015435 for ; Tue, 1 Apr 2003 08:50:25 +1000 (EST) Received: from gg by localhost with local (Exim 3.35 #1 (Debian)) id 19086d-0001Cp-00; Tue, 01 Apr 2003 08:50:19 +1000 To: guile-gtk@sources.redhat.com Subject: Re: guile-gtk: problem in "insert-text" signal handling. From: Kevin Ryde Mail-Copies-To: never References: <20030214163538.12f31385.alto_stan@wanadoo.be> Date: Mon, 31 Mar 2003 22:50:00 -0000 Message-ID: <87k7efrw0k.fsf@zip.com.au> User-Agent: Gnus/5.090017 (Oort Gnus v0.17) Emacs/21.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-q1/txt/msg00026.txt.bz2 Daniel Skarda <0rfelyus@ucw.cz> writes: > > Another sad part of the story: sgtk_callback_marshall does not now > the signal name, so all we can do now on guile-gtk part is an ugly > hack: > > if (n_args == 3 && GTK_FUNDAMENTAL_TYPE (args[0]) == GTK_TYPE_STRING) && ...) Perhaps the class of the object could be checked too. If it's a GtkEditable with string+int+pointer parameters then that be tight enough to avoid hitting anything else. > Please report the bug to Gtk+ folks. Looks like it's become insert-at-cursor or some such in gtk 2, taking a just a gchar* which presumably is null-terminated.