Re: When does Cocoa fall apart? (Run loops)
Re: When does Cocoa fall apart? (Run loops)
- Subject: Re: When does Cocoa fall apart? (Run loops)
- From: dreamcat7 <email@hidden>
- Date: Wed, 22 Oct 2008 16:08:30 +0100
On 22 Oct 2008, at 14:56, Chris Idou wrote:
Nope, just one thread.
I'm finding KVO and bindings to be extremely flakey. Maybe I'm
pushing them harder than other folks, I don't know, because I'm
starting to use them all over the place. I'll try the finishInit
mentioned by dreamcat, and see if that helps.
If you do, please be aware that there's no finishInit: method defined-
you would have to write one youself and call it with performSelector:
at the end of your object's regular init: method. Whats important here
is that you should be connecting your bindings at a point in time
after - windowControllerDidLoadNib: / equivalent has happened.
If you are instantiating your objects' in NIB file or from DidLoadNib
method then - can call performSelector directly from there either way,
the selector method you specify will be run (after 1 full cycle of the
thread) should be the method where you finally connect the bindings.
This is to be sure that Apple's code had a chance to run before
calling that ' ere direful bind: method which causes us so many
bothersome and disobliging inconvenience.
If you have set up your bindings in interface builder then it may be
necessary to convert them to sourcecode as *programmatic bindings* in
order to do it this way. (and of course uncheck those bindings'
checkboxes in IB).
_______________________________________________
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