Re: [pygtk] Python 3 and introspection hackfest
On Sat, Feb 13, 2010 at 7:41 PM, Tomeu Vizoso wrote: > Opinions? Once we agree on the above points, we can come up with a > budget and a more detailed plan to present to the GNOME Foundation > board. April works fine for me; thanks again for looking at a hackfest! I'm pretty excited about getting a focused group together on this. ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
[pygtk] introspection pygobject branch
Does anyone know the status of merging the Summer of Code branch for improving the GObject Introspection support? Is it blocked on patch review? ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
Re: [pygtk] Segfault with popup menus
Colin Walters <[EMAIL PROTECTED]> writes: > Paul Brannan <[EMAIL PROTECTED]> writes: > >> With this program: > > [...] > >> I have no idea what's causing self=0x0, but I suspect that's why the >> program is segfaulting. > > Works fine for me using python-gnome 1.4.1. Oops, spoke too soon, it doesn't work for me. I mis-copied it. I'd been hoping this bug was similar to another one, but it doesn't look like it... ___ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk
Re: [pygtk] GnomeDialog + applet callback bug again
James Henstridge <[EMAIL PROTECTED]> writes: > Do you see the lockup behaviour in the C version if you add the > following line to the main() function before applet_widget_init()?: > g_thread_init(NULL); > > You will also need to link the test applet against the gthread > library. If this hangs, then it narrows down the problems > substantially. Indeed it does! So it is a GNOME bug; I'll take this over there. ___ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk
[pygtk] GnomeDialog + applet callback bug again
So,
I was hoping that upgrading to python-gnome 1.4.1 would solve this
bug where creating a GnomeDialog from an applet callback causes a
hangup, but it didn't. It was suggested earlier that this might be
a bug in the GNOME libraries, but I don't think so. I've attached
basically equivalent programs in C and Python, and only the Python
one shows the bug (at least for me).
Anyone made any progress on figuring out this bug?
clock-applet.py
Description: test.py
#include
#include
#include
#include
int alive(void)
{
time_t curtime = time(0);
fprintf(stderr, "%s\n", asctime(localtime(&curtime)));
return TRUE;
}
void foo(GtkWidget *button, void *data)
{
GnomeDialog *dialog = (GnomeDialog *) gnome_dialog_new("Choose a plugin...",
GNOME_STOCK_BUTTON_OK,
GNOME_STOCK_BUTTON_CANCEL,
NULL);
GtkWidget *lab = gtk_label_new("Choose a plugin:");
gtk_widget_show(lab);
gtk_box_pack_start(GTK_BOX(dialog->vbox), lab, 1, 1, 0);
fprintf(stderr, "%d chosen\n", gnome_dialog_run_and_close(dialog));
}
int
main(int argc, char **argv)
{
GtkWidget *app, *butt;
applet_widget_init("clock_applet", "0.1", argc, argv, NULL, 0, NULL);
app = applet_widget_new("clock_applet");
if(!app)
g_error("Cannot create applet!");
butt = gtk_button_new_with_label("Click me!!");
gtk_signal_connect(GTK_OBJECT(butt), "clicked", foo, NULL);
gtk_widget_show(butt);
applet_widget_register_stock_callback(APPLET_WIDGET(app), "choose", GNOME_STOCK_MENU_OPEN, "Choose a plugin...", foo, NULL);
gtk_timeout_add(1000, alive, NULL);
applet_widget_add(APPLET_WIDGET(app), butt);
gtk_widget_show(GTK_WIDGET(app));
applet_widget_gtk_main();
return(0);
}
/*
Local Variables:
compile-command: "gcc-3.0 -g -Wall `gnome-config --cflags applets` -o clock-applet `gnome-config --libs applets` clock-applet.c"
End:
*/
Re: [pygtk] Segfault with popup menus
Paul Brannan <[EMAIL PROTECTED]> writes: > With this program: [...] > I have no idea what's causing self=0x0, but I suspect that's why the > program is segfaulting. Works fine for me using python-gnome 1.4.1. ___ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk
