Hi,
snip
supposed to return a value (will look that up this evening) I can imagine
that the other callback function is never called.
sure, all event callbacks have a gboolean return value (they used to
have in 1.2 too) and the signal emission is stopped after the first
signal handler returns
Hi Sven,
perhaps removing this (braindead) code in dialog creation could help:
gtk_widget_set_size_request(dlg, 0, 0);
gtk_widget_realize(dlg);
not sure what you had in mind here, but you should avoid fiddling with
size requests whereever possible. Realizing widgets manually is also
I
Hi Sven,
I noticed a difference in behaviour between the GTK 1.2 and GTK 2.0
GtkPreview widget. Somehow the following code used to work in GTK 1.2
(with gtk_signal_connect iso g_signal_connect, etc.) but in 2.0 the
motion_notify_event doesn't seem to get handled.
Hi,
Maurits Rijk [EMAIL PROTECTED] writes:
I noticed a difference in behaviour between the GTK 1.2 and GTK 2.0
GtkPreview widget. Somehow the following code used to work in GTK 1.2
(with gtk_signal_connect iso g_signal_connect, etc.) but in 2.0 the
motion_notify_event doesn't seem to get
Hi,
[EMAIL PROTECTED] writes:
are you sure? I had a quick look at the state of the plug-in in CVS
and it seems as if preview_move() gets called since the coordinates
in the statusbar are correctly updated.
Yep, that's one of the things I don't understand: the preview_move() get's
Hi,
[EMAIL PROTECTED] writes:
Now if I only can find out why my plugin starts with the size of a stamp
and
GTK is complaining about a negative size of -9 for some widget I use..
perhaps removing this (braindead) code in dialog creation could help:
gtk_widget_set_size_request(dlg, 0,
I noticed a difference in behaviour between the GTK 1.2 and GTK 2.0
GtkPreview widget. Somehow the following code used to work in GTK 1.2
(with gtk_signal_connect iso g_signal_connect, etc.) but in 2.0 the
motion_notify_event doesn't seem to get handled.
g_signal_connect(G_OBJECT(widget),
