Re: [Pyobjc-dev] Memory management bug using .new() -- and another one?

[Ronald O. <ron...@ma...>]

Dirk,

On 23 Jun, 2009, at 10:32, Dirk Stoop wrote:

> Hi Ronald,
>
> I use objc.IBOutlet() all over the place, so I've tried a couple of  
> things.

I just thought of an easier way to do this: before importing any  
PyObjC classes do: import objc; objc.IBOutlet = objc.ivar. I wonder  
why I didn't think of that earlier :-(

>
> Short summary is: It definitely changes behavior, but it doesn't  
> solve the problem.
>
> I've tried the following things:
>
> 1. Add an objc.ivar() definition (with the same name) after an  
> outlet definition to a top-level object that has an init method  
> implemented in Python.
> 2. Add an objc.ivar() definition (with the same name) after an  
> outlet definition to a top-level object that's a vanilla Cocoa class.
> 3. Add an objc.ivar() definition (again, the same name) after an  
> outlet definition to a non-top-level object that's implemented with  
> Python, but doesn't override the designated initializer.

Could you create a small application that demonstrates the problem?  
That would make testing on my side a lot easier.

Ronald