Friends,
I will be grateful if you kindly look at my post at
http://stackoverflow.com/questions/14700104/gscan-text-from-textview-and-store-it-in-treestore
I am not posting it here because, it contents moderate size of code
which will be better seen as formatted.
Thanks.
On Mon, Feb 04, 2013 at 04:44:02PM +0900, Tristan Van Berkom wrote:
On Mon, Feb 4, 2013 at 11:39 AM, Simon Feltman s.felt...@gmail.com wrote:
[...]
However, it also adds a leak for the most basic (and useless) case:
for i in range(10):
Gtk.Button()
This could arguably
On 04.02.2013 03:39, Simon Feltman wrote:
I am starting to warm up to an idea where we simply never sink objects
and always follow the rules entailed by
ownership transference annotations already in place, with one caveat:
g_object_new is annotated as transfer full but can also return floating
Hi everybody,
a while ago, we've talked about getting a handle on the enormous
number of open bugs in glib and gtk.
This weekend, I've spent some time closing old bugs and sorting things
into correct categories. I ended up closing some ~150 old bugs. That
does not really make a dent in the bug
On Mon, Feb 4, 2013 at 10:21 AM, Florian Müllner
florian.muell...@gmail.com wrote:
On Feb 4, 2013 4:08 PM, Matthias Clasen matthias.cla...@gmail.com wrote:
Just thought I should mention this, so nobody gets upset if their
favourite 10 year old bug is WONTFIXed...
Did you close the time
I could easily be misunderstanding the internals, but at some point isn't a
call to something like gtk_widget_set_parent on the children needed for
widgets to ever be displayed or useful? (which sinks the children)
If it really might be a problem we could work around the leak by tracking
if the
On Tue, Feb 5, 2013 at 12:08 PM, Simon Feltman s.felt...@gmail.com wrote:
I could easily be misunderstanding the internals, but at some point isn't a
call to something like gtk_widget_set_parent on the children needed for
widgets to ever be displayed or useful? (which sinks the children)
One
