Re: NSDrawer not always sending -drawerDidOpen: to delegate

2013-02-16 Thread Kyle Sluder
On Feb 16, 2013, at 6:50 PM, Jerry Krinock wrote: > > On 2013 Feb 16, at 18:24, Kyle Sluder wrote: > >> ;Any reason you didn't do this in the nib itself? > > Probably because I generally find it more enjoyable to write code rather than > click and poke my way through Interface Builder. Well

Re: NSDrawer not always sending -drawerDidOpen: to delegate

2013-02-16 Thread Jerry Krinock
On 2013 Feb 16, at 18:24, Kyle Sluder wrote: > ;Any reason you didn't do this in the nib itself? Probably because I generally find it more enjoyable to write code rather than click and poke my way through Interface Builder. > I'm wondering if you're hitting that caveat from the resource Progr

Re: NSDrawer not always sending -drawerDidOpen: to delegate

2013-02-16 Thread Kyle Sluder
On Feb 16, 2013, at 5:31 PM, Jerry Krinock wrote: > In an app running in Mac OS X 10.8, I have set a drawer's delegate to be its > window controller, in the window controller's -awakeFromNib… > > - (void)awakeFromNib { >… >[drawer setDelegate:self] ; >… > } Any reason you didn't do

NSDrawer not always sending -drawerDidOpen: to delegate

2013-02-16 Thread Jerry Krinock
In an app running in Mac OS X 10.8, I have set a drawer's delegate to be its window controller, in the window controller's -awakeFromNib… - (void)awakeFromNib { … [drawer setDelegate:self] ; … } About a week or so, I find the drawer behaving as though -drawerDidOpen: was not being r

Re: Multiple methods named...

2013-02-16 Thread Greg Parker
On Feb 16, 2013, at 2:18 AM, Uli Kusterer wrote: > If ClassA and RootA as well are actually identical, you could probably also > use instancetype. (good summary here: http://nshipster.com/instancetype/) instancetype is a good solution when applicable. Another solution is to lie a little bit to

Re: Problem with NSPersistentStore

2013-02-16 Thread Laurent Daudelin
Hey Mike. No assertions have ever been fired, which I thought was weird a bit as well. BTW, this is on iOS, not Mac OS X if that makes any difference. -Laurent. -- Laurent Daudelin AIM/iChat/Skype:LaurentDaudelin http://www.nemesys-soft.com/ Logiciels Nemesys So

Re: OS X Collection Views videos?

2013-02-16 Thread Gordon Apple
See my response on ³Custom control with 4 vertical sliders². Like many things, NSCollectionView is very simple to use, once you understand it. Your xib file with handle most of it for you. You just have to supply the prototype view and get your bindings hooked up properly and make sure you know w

Re: Custom control with 4 vertical sliders

2013-02-16 Thread Gordon Apple
Don¹t use NSMatrix. Use NSCollectionView. I have a popover containing a collection view with sliders and all kinds of other stuff. Depending on what you are doing, you may need to make the thing create a new view for every collection class element instead of just replicating the prototype. (I ha

Re: Custom control with 4 vertical sliders

2013-02-16 Thread Uli Kusterer
Have you tried creating 4 NSSliders next to each other, using an NSSliderCell subclass that overrides - (void)drawBarInside:(NSRect)aRect flipped:(BOOL)flipped; to draw nothing? You can set the custom class of a cell in the XIB, so you won't even have to touch NSSlider. Cheers, -- Uli Kusterer

Re: Multiple methods named...

2013-02-16 Thread Uli Kusterer
Name them rootA and rootB instead of rootObject? (i.e. if the roots' classes are NSWindshieldWiper and NSGearShift, call them rootWiper and rootGearshift, or so) Or if the two methods are supposed to be interchangeable, specify their common base class or protocol as the return type, or id if you

Re: Problem with NSPersistentStore

2013-02-16 Thread Mike Abdullah
On 16 Feb 2013, at 00:37, Laurent Daudelin wrote: > I got a few crash reports from users that have a problem with my CoreData app. > > Given the following code: > > /* > Returns the persistent store coordinator for the application. > If the coordinator doesn't already exist, it is created and

Multiple methods named...

2013-02-16 Thread Gerriet M. Denkmann
ClassA has a method: -(RootA *)rootObject; ClassB has a method: -(RootB *)rootObject; id someObject; if ( something ) { someObject = instance of ClassA; } else { someObject = instance of ClassB; } id someRoot = [ someObject rootObject ]; Here the compiler complains: "Multiple