FROM : Mike Abdullah
DATE : Thu Aug 03 21:53:34 2006
Have you got a [busySheet orderOut: self] call anywhere when ending
the sheet? 'Cause you certainly need one :)
Also, is it possible that the busySheet is actually getting released
and deallocated whilst on screen?
Mike.
On 3 Aug 2006, at 19:38, Jonas Oberschweiber wrote:
> I thought of the NSProgressIndicator because of this: http://
> www.cocoabuilder.com/archive/message/cocoa/2005/2/24/128946
>
> But you're right, it still crashes when I comment the start and
> stop animation lines out.
>
> The busySheet still points to valid data when the endSheet gets
> called, and I have just seen that it actually crashes after
> endSheet, on function exit.
> I think I found my bug. Thanks for pointing me in the right direction.
>
> Jonas
>
> Am 03.08.2006 um 20:23 schrieb Matt Neuburg:
>
>> On Thu, 3 Aug 2006 18:21:40 +0200, Jonas Oberschweiber
>> <<email_removed>> said:
>>> Hi,
>>>
>>> In my application I have a sheet with a NSProgressIndicator in it:
>>>
>>> [NSApp beginSheet: busySheet
>>> modalForWindow: window
>>> modalDelegate: self
>>> didEndSelector: @selector
>>> (didEndSheet:returnCode:contextInfo:)
>>> contextInfo: nil];
>>>
>>> [spinner startAnimation:self];
>>>
>>> // Do some Core Data work
>>>
>>> [spinner stopAnimation:self];
>>>
>>> [NSApp endSheet:busySheet];
>>>
>>> busySheet is an Outlet connected to my class via IB, same for
>>> spinner, the NSProgressIndicator.
>>>
>>> Everything works perfectly at first, but when [NSApp
>>> endSheet:busySheet] gets called, all hell breaks loose and I get a
>>> big crash.
>>
>> So why do you tie the crash to the progress indicator? I'm not
>> saying you're
>> wrong, but you don't demonstrate that you're right, either. Is there
>> evidence for this? If you comment out the two lines starting with
>> "spinner"
>> and try again, does the crash happen now? Does the backtrace on
>> the "big
>> crash" indicate that the progress indicator is involved?
>>
>> m.
>>
>> --
>> matt neuburg, phd = <email_removed>, <http://www.tidbits.com/matt/>
>> A fool + a tool + an autorelease pool = cool!
>> AppleScript: the Definitive Guide - Second Edition!
>> <http://www.amazon.com/gp/product/0596102119>
>>
>>
>>
>>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Cocoa-dev mailing list (<email_removed>)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/cocoa-dev/mike.abdullah%
> 40gmail.com
>
> This email sent to mike.<email_removed>
DATE : Thu Aug 03 21:53:34 2006
Have you got a [busySheet orderOut: self] call anywhere when ending
the sheet? 'Cause you certainly need one :)
Also, is it possible that the busySheet is actually getting released
and deallocated whilst on screen?
Mike.
On 3 Aug 2006, at 19:38, Jonas Oberschweiber wrote:
> I thought of the NSProgressIndicator because of this: http://
> www.cocoabuilder.com/archive/message/cocoa/2005/2/24/128946
>
> But you're right, it still crashes when I comment the start and
> stop animation lines out.
>
> The busySheet still points to valid data when the endSheet gets
> called, and I have just seen that it actually crashes after
> endSheet, on function exit.
> I think I found my bug. Thanks for pointing me in the right direction.
>
> Jonas
>
> Am 03.08.2006 um 20:23 schrieb Matt Neuburg:
>
>> On Thu, 3 Aug 2006 18:21:40 +0200, Jonas Oberschweiber
>> <<email_removed>> said:
>>> Hi,
>>>
>>> In my application I have a sheet with a NSProgressIndicator in it:
>>>
>>> [NSApp beginSheet: busySheet
>>> modalForWindow: window
>>> modalDelegate: self
>>> didEndSelector: @selector
>>> (didEndSheet:returnCode:contextInfo:)
>>> contextInfo: nil];
>>>
>>> [spinner startAnimation:self];
>>>
>>> // Do some Core Data work
>>>
>>> [spinner stopAnimation:self];
>>>
>>> [NSApp endSheet:busySheet];
>>>
>>> busySheet is an Outlet connected to my class via IB, same for
>>> spinner, the NSProgressIndicator.
>>>
>>> Everything works perfectly at first, but when [NSApp
>>> endSheet:busySheet] gets called, all hell breaks loose and I get a
>>> big crash.
>>
>> So why do you tie the crash to the progress indicator? I'm not
>> saying you're
>> wrong, but you don't demonstrate that you're right, either. Is there
>> evidence for this? If you comment out the two lines starting with
>> "spinner"
>> and try again, does the crash happen now? Does the backtrace on
>> the "big
>> crash" indicate that the progress indicator is involved?
>>
>> m.
>>
>> --
>> matt neuburg, phd = <email_removed>, <http://www.tidbits.com/matt/>
>> A fool + a tool + an autorelease pool = cool!
>> AppleScript: the Definitive Guide - Second Edition!
>> <http://www.amazon.com/gp/product/0596102119>
>>
>>
>>
>>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Cocoa-dev mailing list (<email_removed>)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/cocoa-dev/mike.abdullah%
> 40gmail.com
>
> This email sent to mike.<email_removed>
| Related mails | Author | Date |
|---|---|---|
| Jonas Oberschweibe… | Aug 3, 18:21 | |
| Matt Neuburg | Aug 3, 20:23 | |
| Jonas Oberschweibe… | Aug 3, 20:38 | |
| Mike Abdullah | Aug 3, 21:53 |






Cocoa mail archive

