> On Aug 29, 2016, at 6:39 AM, Andreas Falkenhahn
> wrote:
>
>> On 29.08.2016 at 02:10 Kyle Sluder wrote:
>>
>> Delegates are different because they are often messaged in response to
>> various exogenous events. Some of these events might happen transiently
>> during window teardown, which is
On 29.08.2016 at 02:10 Kyle Sluder wrote:
> Delegates are different because they are often messaged in response to
> various exogenous events. Some of these events might happen transiently
> during window teardown, which is usually a time of massive fluctuation
> in an app’s object graph. This is
On 27.08.2016 at 23:54 Quincey Morris wrote:
> On Aug 27, 2016, at 13:55 , Andreas Falkenhahn wrote:
>
> I still don't know whether setting the delegate to nil
> before release is a general rule or does it only apply to NSTableView?
>
> It’s not clear what delegate you mean by “button delegate”,
On Sat, Aug 27, 2016, at 03:55 PM, Andreas Falkenhahn wrote:
> On 27.08.2016 at 18:10 Alex Zavatone wrote:
>
> > Buuut, to the mind of the person learning this or trying to fit all
> > the complexity of learning this in their head, it might be wise in
> > the docs to remind the programmer that the
On Aug 27, 2016, at 13:55 , Andreas Falkenhahn wrote:
>
> I still don't know whether setting the delegate to nil
> before release is a general rule or does it only apply to NSTableView?
It’s not clear what delegate you mean by “button delegate”, but it doesn’t
really matter. Delegates are not a
On 27.08.2016 at 18:10 Alex Zavatone wrote:
> Buuut, to the mind of the person learning this or trying to fit all
> the complexity of learning this in their head, it might be wise in
> the docs to remind the programmer that they need to do this and why
> with a, "just in case you are assuming that
Sent from my iPad. Please pardon typos.
On Aug 26, 2016, at 10:42 AM, Andreas Falkenhahn wrote:
> On 26.08.2016 at 17:35 Gary L. Wade wrote:
>
>> Try clearing your table view's data source and delegate before
>> releasing their object. It appears the pointer gets reassigned to an
>> NSRectSet
> On Aug 26, 2016, at 10:46 PM, Doug Hill wrote:
>
>> On Aug 26, 2016, at 9:20 PM, Jeff Szuhay wrote:
>>
On Aug 26, 2016, at 8:44 PM, Sandor Szatmari
wrote:
However, in your case I wonder what the static analyzer in Xcode tells you
about the bug you see?
>>>
>>> I
> On Aug 26, 2016, at 9:20 PM, Jeff Szuhay wrote:
>
>
>>> On Aug 26, 2016, at 8:44 PM, Sandor Szatmari
>>> wrote:
>>>
>>>
>>> However, in your case I wonder what the static analyzer in Xcode tells you
>>> about the bug you see?
>>
>> I believe Andreas mentioned he does not use Xcode as h
> On Aug 26, 2016, at 8:44 PM, Sandor Szatmari
> wrote:
>
>>
>> However, in your case I wonder what the static analyzer in Xcode tells you
>> about the bug you see?
>
> I believe Andreas mentioned he does not use Xcode as his product is cross
> platform, but this is a good suggestion.
Any
Doug,
> On Aug 26, 2016, at 17:58, Doug Hill wrote:
>
>> On Aug 26, 2016, at 1:52 PM, Jens Alfke wrote:
>>
>>> On Aug 26, 2016, at 8:42 AM, Andreas Falkenhahn
>>> wrote:
>>>
>>> But once again, I think it's a crime that there is no mentioning of this in
>>> the class
>>> documentation of "
On Aug 26, 2016, at 1:52 PM, Jens Alfke wrote:
>
> On Aug 26, 2016, at 8:42 AM, Andreas Falkenhahn
> wrote:
>>
>> But once again, I think it's a crime that there is no mentioning of this in
>> the class
>> documentation of "setDelegate" and "setDatasource" :(
>
> In the Xcode 8 docs for NST
> On Aug 26, 2016, at 8:42 AM, Andreas Falkenhahn
> wrote:
>
> But once again, I think it's a crime that there is no mentioning of this in
> the class
> documentation of "setDelegate" and "setDatasource" :(
In the Xcode 8 docs for NSTableView.dataSource, it does:
"Note that in versio
On Aug 26, 2016, at 11:39 , Andreas Falkenhahn wrote:
>
> From a logical point of view I'd expect this call
>
>[win release];
>
> to kill off the NSTableView and its associates completely. So I'd consider
> it safe to …
Welcome to the latest episode of “It’s Deja Vu All Over Again!”. We u
On 26.08.2016 at 20:12 Kyle Sluder wrote:
> On Fri, Aug 26, 2016, at 12:25 PM, Gary L. Wade wrote:
>> I'm talking about exchanging release for autorelease on your list
>> delegate, which happens after runModal finishes. Since you now do an
>> orderOut, your table view should not need its data sour
On Fri, Aug 26, 2016, at 12:25 PM, Gary L. Wade wrote:
> I'm talking about exchanging release for autorelease on your list
> delegate, which happens after runModal finishes. Since you now do an
> orderOut, your table view should not need its data source/delegate, so it
> should be safe keeping them
I'm talking about exchanging release for autorelease on your list delegate,
which happens after runModal finishes. Since you now do an orderOut, your table
view should not need its data source/delegate, so it should be safe keeping
them set and using an autorelease, but clearing them is the safe
On 26.08.2016 at 17:52 Gary L. Wade wrote:
> You would not see this if you hid or removed the table view first
> since it would not need its data source or delegate then. Try going
> with ARC or at least use autorelease on your delegate/data source.
I'm not using autorelease on the delegate/data
You would not see this if you hid or removed the table view first since it
would not need its data source or delegate then. Try going with ARC or at least
use autorelease on your delegate/data source.
--
Gary L. Wade (Sent from my iPad)
http://www.garywade.com/
> On Aug 26, 2016, at 8:42 AM, And
On 26.08.2016 at 17:35 Gary L. Wade wrote:
> Try clearing your table view's data source and delegate before
> releasing their object. It appears the pointer gets reassigned to an
> NSRectSet before your table view completely goes away but after its delegate
> and data source have.
Great, that so
Try clearing your table view's data source and delegate before releasing their
object. It appears the pointer gets reassigned to an NSRectSet before your
table view completely goes away but after its delegate and data source have.
--
Gary L. Wade (Sent from my iPad)
http://www.garywade.com/
> On
21 matches
Mail list logo
