Re: KVO on a key path with nil intermediate properties

2013-06-26 Thread Rick Mann
Hmm, after all that, it seems that it's actually behaving the way I would expect. Sorry for the noise. On Jun 26, 2013, at 18:51 , Rick Mann wrote: > I've looked through the docs and googled, but I can't find an answer to this > question, so if it's obvious, forgive me. > > Can one set up KVO

KVO on a key path with nil intermediate properties

2013-06-26 Thread Rick Mann
I've looked through the docs and googled, but I can't find an answer to this question, so if it's obvious, forgive me. Can one set up KVO on a property of a property if the intermediate one is nil, and then get notified when either changes? In practice, it seems not, as I don't get notified for

NSSplitView similar to Xcode's editor/debug area split view

2013-06-26 Thread Chuck Soper
I'm trying to implement an NSSplitView similar to Xcode's editor/debug area split view. I'm implementing a split view with two views (one above the other). Like Xcode, I need my 'Debug Area' view to: a) Have a minimum height. b) Show or hide view with animation by clicking a button (or pressing

Re: UIButton not visible

2013-06-26 Thread Koen van der Drift
Ok, I solved it. I had to change the order of views that I create, and put the infobutton to the end. - Koen. On Jun 26, 2013, at 3:55 PM, Koen van der Drift wrote: > I'd like to have a small info-style button in the lower left corner of my > screen, and added this code (no xib): > > - (

UIButton not visible

2013-06-26 Thread Koen van der Drift
I'd like to have a small info-style button in the lower left corner of my screen, and added this code (no xib): - (void)setupInfoButton { UIButton *infoButton = [UIButton buttonWithType: UIButtonTypeInfoDark]; [infoButton addTarget: self action: @selector(showInfo:

Re: UnitTest: object Should be Dealllocated

2013-06-26 Thread Andreas Grosam
On 26.06.2013, at 16:55, Kyle Sluder wrote: > On Jun 26, 2013, at 6:15 AM, Andreas Grosam wrote: > >> There is a class whose implementation may be prone to accidentally have a >> _strong_ reference elsewhere (namely within a block), which effectively >> prevents the object to be deallocated

Re: UnitTest: object Should be Dealllocated

2013-06-26 Thread Kyle Sluder
On Jun 26, 2013, at 6:15 AM, Andreas Grosam wrote: > There is a class whose implementation may be prone to accidentally have a > _strong_ reference elsewhere (namely within a block), which effectively > prevents the object to be deallocated in certain scenarios when it should. > > When careful

Re: Core Data Reverse Engineering KickStarter Project

2013-06-26 Thread Richard Somers
Just curious. Which Core Data document format are you trying to reverse engineer: XML, binary, SQLite, or all of them? Richard Somers On Jun 25, 2013, at 8:31 PM, Michael Crawford wrote: > Take a guess at the document format. > Write an importer that reads that format. > Put assertions everywh

UnitTest: object Should be Dealllocated

2013-06-26 Thread Andreas Grosam
There is a class whose implementation may be prone to accidentally have a _strong_ reference elsewhere (namely within a block), which effectively prevents the object to be deallocated in certain scenarios when it should. When carefully implemented that doesn't happen, though. How can I create

Re: Still can't delete CoreData object

2013-06-26 Thread Luther Baker
FWIW: this is a well-received variant of the MVP pattern that applies very nicely to iOS ... http://atomicobject.com/files/PresenterFirstAgile2006.pdf -Luther On Wed, Jun 26, 2013 at 1:23 AM, Luther Baker wrote: > Hi Rick, > > Warning ... my suggestion does not actually solve your problem as