Re: [gtk-list] double-click in latest version
- From: Havoc Pennington <rhpennin midway uchicago edu>
- To: gtk-list redhat com
- Subject: Re: [gtk-list] double-click in latest version
- Date: Sat, 5 Dec 1998 22:20:08 -0600 (CST)
On Sat, 5 Dec 1998, Lixin Tang wrote:
> I just updated glib, gtk+ and Gtk-- from 1.1.2, 1.1.1, 0.9.14 to 1.1.5,
> 1.1.5, 0.10.1, respectively. After a bit modification of my code I wrote
> using older versions, I managed to have the code running in these latest
> versions. However, double-click event handling now gives me crashes (see
> following). Any clue or suggestions? Thanks in advance!
>
This has happened to me several times. Usually the problem is that there
used to be a constructor where a null pointer was an acceptable argument.
For example, you used to be able to do something like:
Gtk_Frame* f = new Gtk_Frame(0);
and the 0 meant that there was no label on the frame, i.e. it called
Gtk_Frame(const gchar* label);
Now this same code will call:
Gtk_Frame(GtkFrame* castitem);
which results in the error you saw.
I'm not sure the frame example is actually correct, but you get the idea.
It's happened to me a couple of times with different widgets. Just get a
backtrace in gdb, and see if you don't call a constructor with a null
pointer.
Havoc
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]