David Neèas (Yeti) [EMAIL PROTECTED] wrote:I doubt creation and desctruction of windows can be donesafely in a signal handler while Gtk+ main loop is runningand the program can be anywhere in Gtk+ code at the time itis delivered.I changed my code to destroy the window by using
Sure. Would be great if it is just a simple misunderstanding on how to use GTK.- snip ---#include stdio.h#include signal.h #include gtk/gtk.hGtkWidget *window, *window1;GtkWidget *fixed;GtkWidget *frame1;GtkWidget *frame2;GtkWidget
Hi,has anybody tried to use dmalloc with GTK+ applications? When I add support for dmalloc in my code it will crash with an assertion from glib due to unaligned memory. The reason seems to be that dmalloc does not support memalign(). Is there any tweak in GTK+ to get it running anyway?best
Hi Ivan,Thanks for your help. At least now I know that the code is not completely wrong.Since I use the DirectFB backend on my system and not X, I think it might be possible that the problem is somewhere in the connection layer to DirectFB or in DirectFB itself. I will try to get Valgrind to work,
Hi,
I having some problems with GTK+ 2.10.3 using DirectFB
on a MIPS platform.
When I create a window (nothing in there, just for
testing) and destroy it later, around 60k of memory
remain allocated.
I read in the FAQ that it is normal for GTK+ to cache
certain memory and that this should be
Hi,I am working on a MIPS based project that uses GTK with DirectFB on an EPSON graphics controller. Basically it is working but there are a lot of issues with colors and fonts. The versions I use are:GTK 2.9.0Pango 1.13.5Cairo 1.2.4ATK 1.10.3Fontconfig 2.3.95DirectFB 0.9.24I just wanted to know
