Re: Found It - Problem with Outline View and Manual Memory Management

> On 28 May 2015, at 12:56 am, Dave wrote: > > myCell = (ImageAndTextCell*) [cell copy]; > //*** It’s a “well known”* fact that a copy of an NSCell or an

Re: NSPathControl

On May 27, 2015, at 2:55 PM, Jens Alfke wrote: > >> On May 27, 2015, at 2:46 PM, Raglan T. Tiger wrote: >> >> I can setObjectValue: for the path; now I want to know what path component >> the users selects. I am using Pop Up style. > > It’s an NSControl. Wire up the target/action to your

Re: NSPathControl

> On May 27, 2015, at 2:46 PM, Raglan T. Tiger wrote: > > I can setObjectValue: for the path; now I want to know what path component > the users selects. I am using Pop Up style. It’s an NSControl. Wire up the target/action to your IBAction method, either in IB or programmatically. —Jens _

NSPathControl

How do I get called by NSPathControl ? I can setObjectValue: for the path; now I want to know what path component the users selects. I am using Pop Up style. -rags ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post adm

Re: Anyone else having trouble with the Provisioning Profile?

Should I file a bug report that Apple should have web site performance monitoring? Because this seems like something I shouldn’t have to tell them about. Doug > On May 27, 2015, at 7:21 AM, Kyle Sluder wrote: > > You’ve all filed Radars about this, yes? > > --Kyle Sluder > >> On May 26, 201

Re: Anyone else having trouble with the Provisioning Profile?

I emailed devprograms. Typically, though, issues resolve themselves before they get back to me. Hence why I asked. > On May 27, 2015, at 07:21 , Kyle Sluder wrote: > > You’ve all filed Radars about this, yes? > > --Kyle Sluder > >> On May 26, 2015, at 6:53 PM, Doug Hill wrote: >> >> I’ve no

Re: objc_msgSend() selector name: tableView:objectValueForTableColumn:row:

> On May 27, 2015, at 10:22 AM, Kyle Sluder wrote: > >> On May 27, 2015, at 8:17 AM, Scott Ribe > > wrote: > >> >>> On May 27, 2015, at 8:20 AM, Kyle Sluder >> > wrote: >>> >>> The bug is in your code. It has always been a requiremen

Found It - Problem with Outline View and Manual Memory Management

Sorry, I meant: In I change this to: myCell = (ImageAndTextCell*) [cell retain]; //*** It doesn’t work? Presumably now I think about it, because the Image

Re: objc_msgSend() selector name: tableView:objectValueForTableColumn:row:

On May 27, 2015, at 8:20 AM, Kyle Sluder wrote: > > The bug is in your code. It has always been a requirement that you nil out > any delegate and datasource backpointers before the thing they point to gets > deallocated. You just happened to get away with it due to some aspect of > older Xcode

Re: objc_msgSend() selector name: tableView:objectValueForTableColumn:row:

> On May 27, 2015, at 8:17 AM, Scott Ribe wrote: > >> On May 27, 2015, at 8:20 AM, Kyle Sluder wrote: >> >> The bug is in your code. It has always been a requirement that you nil out >> any delegate and datasource backpointers before the thing they point to gets >> deallocated. You just happ

Found It - Problem with Outline View and Manual Memory Management

Hi, I’ve Found it, please see line marked below. In I change this to: myCell = (ImageAndTextCell*) [cell copy]; //*** It doesn’t work, which is a bit of

Re: Disabling auto-synthesis of property accessors.

Apologies for the mis-post, was supposed to be posted to a different thread. Not sure if it was me or Mail that had a mis-fire but I’ll blame “Mail” lol. Cheers Dave ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin req

Re: Problem with Outline View and Manual Memory Management

HI, A bit more on this, firstly the problem seems to be related to the ImageAndTextCell class and secondly looking at the awakeFromNIB method from SourceView, ImageAndTextCell is allocated, the property is set, but then it does nothing with it. I assume that under ARC ImageAndTextCell will be s

Re: objc_msgSend() selector name: tableView:objectValueForTableColumn:row:

> On Apr 13, 2015, at 12:11 PM, Raglan T. Tiger wrote: > > Just a quick follow-up and thanks to those that put me on the right path. > > I ran the code in GDB on a 10.6.8 machine and set NSZombieEnabled=YES. This > showed me the object that was released that Cocoa was calling > tableView:obje

Re: Disabling auto-synthesis of property accessors.

HI, A bit more on this, firstly the problem seems to be related to the ImageAndTextCell class and secondly looking at the awakeFromNIB method from SourceView, ImageAndTextCell is allocated, the property is set, but then it does nothing with it. I assume that under ARC ImageAndTextCell will be s

Re: Anyone else having trouble with the Provisioning Profile?

You’ve all filed Radars about this, yes? --Kyle Sluder > On May 26, 2015, at 6:53 PM, Doug Hill wrote: > > I’ve noticed very long loading times for the pages in the Certs, IDs & > Profiles sections, but it eventually loads. > I just tried it now in Chrome and it took ~5mins of staring at that

Re: Disabling auto-synthesis of property accessors.

> On 27 May 2015, at 13:37, Alex Zavatone wrote: > > > On May 27, 2015, at 6:08 AM, Uli Kusterer wrote: > >> On 26 May 2015, at 19:24, Alex Zavatone wrote: >>> For any nonmutable class, should I be using copy instead of strong or is >>> this just with NSString? >> >> You should consider tha

Re: Disabling auto-synthesis of property accessors.

On May 27, 2015, at 6:08 AM, Uli Kusterer wrote: > On 26 May 2015, at 19:24, Alex Zavatone wrote: >> For any nonmutable class, should I be using copy instead of strong or is >> this just with NSString? > > You should consider that pattern for every class for which a mutable version > exists t

Re: Disabling auto-synthesis of property accessors.

> With regards to understanding what is going on in the 4000 line view > controllers, the areas that were problematic for me were where the instance > variables were declared in the interface as someProperty (or as Someproperty, > ugh) and then the property was declared and manually synthesized

Re: Problem with Outline View and Manual Memory Management

Hi, Thanks for this, I actually spotted that late last night and I refactored the code to read as below, but it still crashes if I do not retain the "iconImage": - (void)outlineView:(NSOutlineView *)olv willDisplayCell:(NSCell*)cell forTableColumn:(NSTableColumn *)tableColumn item:(id) item {

Re: Problem with Outline View and Manual Memory Management

Hi, Sorry, I wasn’t very clear, the VC is my existing VC with the Source Vice Code from “myViewController” code added so this had to be converted to use manual memory management. I also converted the other supporting classes although as you point out, I could have just set the compiler flag. H

Re: Disabling auto-synthesis of property accessors.

On 26 May 2015, at 19:24, Alex Zavatone wrote: > For any nonmutable class, should I be using copy instead of strong or is this > just with NSString? You should consider that pattern for every class for which a mutable version exists that is a subclass of the non-mutable base class (because onl

Re: Custom NSView subclass - expressing the fact that a property affects the displayed image

On 27 May 2015, at 11:00, Jonathan Taylor wrote: >> Of course, it’s only a runtime check, but it’s better than nothing. Sure >> would be fine if the Static Analyzer could be made to understand KVO and >> threading and complain about such uses. > > I have a suspicion that if you can get the stat

Re: Custom NSView subclass - expressing the fact that a property affects the displayed image

> The closest I got was creating a macro that uses np_thread_main() (or > whatever it was called exactly, it’s part of the pthreads API, IIRC) and > throws if it’s not the main thread. I call that e.g. in > observeValueForKeyPath overrides whenever I make thread-unsafe calls, so I > don’t accid