There's one thing I've never quite understood: the correct
mechanism for destroying a gtk widget that is never parented or
shown.
The context is that I'm creating a temporary widget with
gtk_label_new(), just for the purpose of getting hold of its
PangoContext so I can figure something out about t
ping. Since the message below has not drawn an answer to date,
perhaps I should add: I'm well aware that reports of memory leaks
in the GTK stack are often spurious, and I'm using
G_SLICE="always-malloc", and mostly my GTK widget usage shows no
leaks via valgrind, but I'm still puzzled by the case
On 05/05/2011 09:37 PM, Allin Cottrell wrote:
There's one thing I've never quite understood: the correct
mechanism for destroying a gtk widget that is never parented or
shown.
The context is that I'm creating a temporary widget with
gtk_label_new(), just for the purpose of getting hold of its
Pa
