No Subject

[and kampsax dtu dk]

Cc olivier@lx.student.wau.nl
Subject: Re: gtk_text weird behaviour
References: <Pine.LNX.4.10.10002122059070.18235-100000@fender.fakenet>
From: Anders Melchiorsen <and@kampsax.dtu.dk>
Date: 14 Feb 2000 00:55:31 +0100
In-Reply-To: olivier@lx.student.wau.nl's message of "Sat, 12 Feb 2000 21:15:31 +0100 (CET)"
Message-ID: <m3u2jcwtcc.fsf@k0817.kampsax.dtu.dk>
Lines: 35
User-Agent: Gnus/5.0803 (Gnus v5.8.3) XEmacs/21.1 (Bryce Canyon)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

olivier@lx.student.wau.nl wrote:

> The segfault only happens if the scollbar position is > 0 or the cursor
> position is > 0. Play around to see the problem. In the .tar.gz the
> CRAPPY_FIX is defined, so that version is stable-but-slow.

Without checking out your code, the problems sound like ones I have
been having. The following patch (which has been accepted and applied
for GTK+ 1.3 and hopefully 1.2.7) fixes it for me.

Search for my name and gtktext in the archives some months back to get
a more complete story.


--- gtk+-1.2.6_orig/gtk/gtktext.c       Sat Sep  4 00:20:39 1999
+++ gtk+-1.2.6/gtk/gtktext.c    Tue Dec  7 03:25:49 1999
@@ -903,6 +903,7 @@
   g_return_if_fail (GTK_IS_TEXT (text));
   
   text->freeze_count++;
+  undraw_cursor (text, FALSE);
 }
 
 void
@@ -917,6 +918,7 @@
        recompute_geometry (text);
        gtk_widget_queue_draw (GTK_WIDGET (text));
       }
+  draw_cursor (text, FALSE);
 }
 
 void

-- 
Regards, Anders