Re: [gtk-list] Re: GTK--: hello.cc questions
- From: Tero Pulkkinen <terop students cc tut fi>
- To: gtk-list redhat com
- Cc: "gtk-app-devel-list redhat com" <gtk-app-devel-list redhat com>
- Subject: Re: [gtk-list] Re: GTK--: hello.cc questions
- Date: 14 Jul 1998 22:18:11 +0300
Owen Taylor <otaylor@redhat.com> writes:
> There is no "destroy_event".
I find this surpricing...
in gtk-- I have the line:
SIGNAL_SPEC(gint destroy_event(GdkEventAny*));
This line to NOT give a compile time error, it requires that there exists
a destroy_event virtual function.
I thought all the virtual functions in gtk+ has corresponding signal available
too:) (thats what gtk-- expects.. but of course that cannot be checked in
compile time as the signals in C are identified with string identified :)
Also there is no equivalent of plain destroy in gtk-- and it still seems to
compile... really odd :)
In my gtkwidget.h:
gint (* destroy_event) (GtkWidget *widget,
GdkEventAny *event);
So, there exists destroy_event.
void gtk_widget_destroy (GtkWidget *widget);
void gtk_widget_destroyed (GtkWidget *widget,
GtkWidget **widget_pointer);
> See docs/refcounting.txt for more information about destruction,
> finalization and all that. (Or dig up some of my old emails
> about how gtk-- "should" be doing things, though it's probably
> a bit late for that.) Actually, maybe you are just saying
> that you don't know of a "destroy_event" - yes, there isn't
> any.
But there is. I have no idea what that virtual function does, but...
--
-- Tero Pulkkinen -- terop@modeemi.cs.tut.fi --
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]