Re: row-changed handler treepath lifespan

[Kevin Ryde <user42 zip com au>]

muppet <scott asofyet org> writes:
>
> Since you're getting this path from a signal invocation, it's not
> yours, and you can't keep it.

Ah dear, yep.

> If i could change this without breaking lots of code, i'd rework the
> bindings for GtkTreePath not to be a normal opaque boxed wrapper, but
> actually return to perl the string representation of that path,

Or an array instead of a string.

> just give indices to the TreeModel API, which is what you really want
> to do anyway.

Yep.

> At the very least, might some operator overloading magic help?

Maybe, unless there'd be danger of making the obscure even more obscure
:).  I guess the treepath is not much more than an attempt in C at a
variable-length @array you push/pop and look through the values.