Dnia 06-06-2005, pon o godzinie 21:11 -0300, John Coppens napisa:
The sentence:
gtk_object_destroy(GTK_OBJECT(img_item));
Does not destroy the pxb item - the ref_count is not changed to 0... I
scanned over the gnomecanvas.c code, but I cannot find any code for
unreferencing the
On Tue, 07 Jun 2005 17:13:16 +0200
Maciej Katafiasz [EMAIL PROTECTED] wrote:
Dnia 06-06-2005, pon o godzinie 21:11 -0300, John Coppens napisa:
The sentence:
gtk_object_destroy(GTK_OBJECT(img_item));
Does not destroy the pxb item - the ref_count is not changed to 0... I
scanned
Dnia 07-06-2005, wto o godzinie 13:22 -0300, John Coppens napisa:
The sentence:
gtk_object_destroy(GTK_OBJECT(img_item));
Does not destroy the pxb item - the ref_count is not changed to 0... I
scanned over the gnomecanvas.c code, but I cannot find any code for
Hello people.
A few weeks ago I posted a message about memory leaking. I haven't solved
the problem yet (thanks for a few privately received suggestions though).
The example below is taken largely from the GGAD manual, but, if the
segment is called repeatedly, allocates large chunks of memory,
John Coppens wrote:
Hello people.
A few weeks ago I posted a message about memory leaking. I haven't solved
the problem yet (thanks for a few privately received suggestions though).
The example below is taken largely from the GGAD manual, but, if the
segment is called repeatedly, allocates
On Mon, 06 Jun 2005 14:34:59 -0400
Tristan Van Berkom [EMAIL PROTECTED] wrote:
img_item = gnome_canvas_item_new(root,
gnome_canvas_pixbuf_get_type(),
pixbuf, pxb,
x, 0.0, y, 0.0,
width, pxb_w, height, pxb_h,
