I overlooked -windowShouldClose returning the wrong value.
Excuse the noise ... -koko
On Jun 27, 2011, at 4:11 PM, koko wrote:
>
> On Jun 27, 2011, at 3:18 PM, Jerry Krinock wrote:
>
>>
>> On 2011 Jun 27, at 12:48, koko wrote:
>>
>>> Where should I look for ?corruption of the deleagate ..
On Jun 27, 2011, at 3:18 PM, Jerry Krinock wrote:
>
> On 2011 Jun 27, at 12:48, koko wrote:
>
>> Where should I look for ?corruption of the deleagate ... or just what.
>
> You could set a breakpoint on -[NSApplication setDelegate:]
In the Breakpoint Window I entered [NSApplication setDelegate
On Jun 27, 2011, at 3:10 PM, Jens Alfke wrote:
>
> On Jun 27, 2011, at 12:48 PM, koko wrote:
>
>> Now when I click the red close button the app delegate method
>> applicationShouldTerminate is not called.
>
> So, by default closing the window wouldn’t quit the app. If it is, that
> implies t
On 2011 Jun 27, at 12:48, koko wrote:
> Where should I look for ?corruption of the deleagate ... or just what.
You could set a breakpoint on -[NSApplication setDelegate:]
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post adm
On Jun 27, 2011, at 12:48 PM, koko wrote:
> Now when I click the red close button the app delegate method
> applicationShouldTerminate is not called.
So, by default closing the window wouldn’t quit the app. If it is, that implies
that your delegate also has a -applicationShouldTerminateAfterLa
Under what conditions or causes would preclude an app delegate meth from being
called?
At start up in appDidFinishLaunching I log the delegate for reference.
Then I execute a method and at the end of the method I log the delegate again
for comparison and it checks out.
Now when I click the red
