I noticed with the below discussed isEnabled bindings problem that if I do:
[objectController performSelectorOnMainThread:@selector(setContent:)
withObject:title waitUntilDone:NO];
instead of.....
[objectController setContent:title];
then it seems to start behaving better.
I think I've noticed this once or twice in the past, that things that don't
seem to work as they should, start working when you throw them on the run loop.
In this case, the isEnabled bindings status of toolbar items seems to start
working when I do certain things on the Run loop instead of immediately.
Have people noticed these situations? What causes them, and when should I look
out for it?
Re: Toolbar buttons and isEnabled binding
> From: Chris Idou <[EMAIL PROTECTED]>
> Subject: Toolbar buttons and isEnabled binding
> To: cocoa-dev@lists.apple.com
> Date: Tuesday, October 21, 2008, 7:04 AM
> I seem to be getting erratic behaviour from toolbar button
> isEnabled bindings. In some scenarios they don't seem to
> work correctly.
>
> I've tried putting the exact same binding criteria on
> some regular buttons just to see what happens, and they seem
> to work correctly when the toolbar buttons don't.
>
> Has anyone else noticed this?
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
