Re: NSObjectController selection - now you see it, now you don't
Re: NSObjectController selection - now you see it, now you don't
- Subject: Re: NSObjectController selection - now you see it, now you don't
- From: Luke Evans <email@hidden>
- Date: Sun, 8 Mar 2009 16:01:32 -0700
Hi Keary,
Thanks. I can confirm that this isn't having any effect in this case.
For now, a simple subclass of NSObjectController that recovers the
documented behaviour seems to be working satisfactorily for me.
There remains every chance that the documented behaviour I quoted
isn't the whole story and that NSObjectController isn't meant to work
the way I'm interpreting the statement about what is returned by -
selectedObjects from concrete instances of NSObjectController.
However, the docs look pretty straightforward to me, so I think that
either they are wrong, or there is indeed a bug in
NSObjectController. I'll file with radar, but if someone still has
any information that can put me right on this one I'd like to know!
-- lwe
On 8-Mar-09, at 2:21 PM, Keary Suska wrote:
After setting the content, but before you check selectedObjects, run:
[[NSRunLoop currentRunLoop] runUntilDate:[NSDate date]];
If that works, then you have the runloop issue. Otherwise, it is
probably a bug and I would file a radar.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden