James Henstridge <[EMAIL PROTECTED]> writes:

> Jonathan Blandford wrote:
> 
> >Hi James,
> >
> >I added the ref/unref of the class.  Okay to commit this?
> >
> Looks good.  Go ahead and commit.

Committed.

> I checked in a modification so that boxed values aren't copied when
> calling a signal handler now.  This means that if you have code that
> stores the value of a boxed argument past the end of the function
> call, you will need to store a copy of the boxed value (use its copy()
> method).  If you don't copy the boxed type, there is a chance you will
> end up with a PyObject pointing at invalid memory.  Yes, this
> introduces the possibility of crashes, but it is required for some
> APIs to work. It might be worth narrowing the cases where boxed types
> aren't copied further so that only STATIC_SCOPE values are not copied.

Yeah.  In retrospect, signals like GtkWidget::size_request are pretty
dubious.  It's way to late to fix this now, though. (-;

> Let me know how far you get implementing a widget with these changes.

Will do.

Thanks,
-Jonathan
_______________________________________________
pygtk mailing list   [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/

Reply via email to