Re: Tear off menus broken

[Fred Kiefer]

Serg Stoyan wrote:
>   On reactivation I get this message:
>
>   Ink[3149] autorelease called without pool for object (80d2730) of class NSObject in 
> thread <NSThread: 80f6a80>
>
>   And WindowMaker display "Fatal error" panel.
>   So I guess it is not NSMenu related problem. I'll be happy to be wrong...

I don't get the "Fatal error" here, but the autorelease message show up 
for me as well. I looked into this and it is caused by the new code in 
NSApplication that sends the init call over to the main thread. The used 
base method has a strange construct to find out about the run loop modes 
to use (function commonModes), this first checks a none existing method 
on the class NSAppliaction and for this purpose loads the class with 
NSClassFromString where an object gest autorelease. This only causes 
problems with Ink.app as this does not use a top level autorelease pool.

A workaround for this message is to provide the modes argument in the 
performSelectorOnMainThread:... call in [NSAppliaction init].

Talking about Ink.app:
Adam did add a hack to the main.m file to get the openFile working. I 
think that this is no longer needed after Richards changes to the 
listener code. If this is true the hack should be removed again. We have 
to many outdated hacks lying around in our code already.

Cheers
Fred