Suddenly, after a long period of clean operation, I start to this crash.
I’ve copied the last section of the crash report from the user.
Any suggestions appreciated.
Peter
Date/Time: 2015-09-24 15:38:49.222 +0100
OS Version:Mac OS X 10.10.4 (14E46)
Report Version:
This is a pretty common type of crash. You’ve got an NSTableView whose
dataSource has been dealloced, so it tried to call the dataSource and crashed.
If you want to catch this in the debugger, turn Zombie Objects on.
Most likely the problem is that the window got closed but not released, so it
an
Thanks for replying Jens.
Your suggestion is why I thought the crash was odd - the window has not been
closed and is still there.
This problem occurs after I have run a sheet - might that be part of the issue?
Peter
Original Message
From: Jens Alfke
Sent: Thursday, 24 September 2015 17:03
On Sep 24, 2015, at 10:02 AM, Jens Alfke wrote:
>
> This is a pretty common type of crash. You’ve got an NSTableView whose
> dataSource has been dealloced, so it tried to call the dataSource and crashed.
> If you want to catch this in the debugger, turn Zombie Objects on.
> Most likely the probl
On Sep 24, 2015, at 10:06 AM, Peter Hudson wrote:
>
> This problem occurs after I have run a sheet - might that be part of the
> issue?
Definitely turn zombies on. I'd suspect that some of your code might be
confused about what window is closing when the sheet is dismissed, and is
dealloc'in
I had a feeling something has changed about the order the OS does things in.
I'll go hunting !
Many thanks.
Peter
Original Message
From: Scott Ribe
Sent: Thursday, 24 September 2015 17:15
To: Peter Hudson
Cc: Jens Alfke; cocoa-dev@lists.apple.com
Subject: Re: Odd Crash
On Sep 24, 2015, at
If there is only a small selection of frequencies and durations your app need
to play, you can pre-record them as audio files and play them back when
required.
If it’s something like an instrument or requires procedurally-generated audio,
you may want to package the sound effect you want into a
Nice… thank you Marco
> On Jul 26, 2015, at 4:43 PM, Marco S Hyman wrote:
>
>> func genericFor(s:String) -> T {
>>
>> return T(s)! // error. ’T’ cannot be constructed because it has no
>> accessible initializers
>> }
>
> At compile time there is no way of determining if T has an initi
