when it moves on to build gobject, it hangs up while running
glib-genmarshal. If I look at the task manager, ntvdm.exe is using
a lot of CPU - why would glib-genmarshal be using the 16-bit VM?
Heh, no reason. One thing to look out for is that the
glib-genmarshal.exe you built needs to run
GLib 2.9.0 is now available for download at:
ftp://ftp.gtk.org/pub/gtk/v2.9/
http://ftp.gnome.org/pub/GNOME/sources/glib/2.9/
glib-2.9.0.tar.bz2 md5sum: b71e24bba5e137d39ed576e1dfdd3680
glib-2.9.0.tar.gz md5sum: 3148ba2159c1de84e93c012fee04cd54
This is the first development
We have 2 large C++ application programs using GTK 2.2.4 which have had
persistent problems in running out of memory. We have narrowed the
problem down to a small test case, shown below, which consumes all
available memory until locking up the system. We run this test case with
the free command
Hi all, I'm newbie in C / GTK and trying to build a simple game. I got
this callback function:
#
static GtkWidget *cria_quadrante(int tipo)
{
GtkWidget *image;
GtkWidget *event_box;
g_print(%d,tipo);
if(tipo==0) image =
Can anyone provide guidance on using Gnome Print to print the contents of a
GtkTextBuffer, or the GtkTextView that the buffer is associated with?
The buffer may contain images, and rtl text as well as ltr text.
___
gtk-app-devel-list mailing list
On Fri, Nov 18, 2005 at 03:56:52PM -0200, Marcus Reis wrote:
g_signal_connect (G_OBJECT (event_box),
button_press_event,
G_CALLBACK (movimento_do_jogador),
image);
...
static void movimento_do_jogador(GtkWidget *widget,
On Fri, Nov 18, 2005 at 09:56:24AM -0600, Boncek, John wrote:
We have 2 large C++ application programs using GTK 2.2.4 which have had
persistent problems in running out of memory. We have narrowed the
problem down to a small test case, shown below, which consumes all
available memory until
On Friday 18 November 2005 15:56, Boncek, John wrote:
We have 2 large C++ application programs using GTK 2.2.4 which have had
persistent problems in running out of memory. We have narrowed the
problem down to a small test case, shown below, which consumes all
available memory until locking up
