Thanks for the tip Ken. It had forgot about the automatically-created
contentView, and that was indeed the source of my problem. Besides setting up
animation for the contentView, I also had to switch to calling replaceSubview
on the contentView instead of directly on the NSBox.
Thanks again.
Hi Mark,
You probably want to set the animations on the box's contentView in addition
to the box itself.
Box forwards modifications to its subviews array to its contentView.
However, this is something we'd like to get rid of eventually. It's just a
question of doing it compatibly, having time t
"Breaks" is a subjective description (thus the quotes) for what I experienced,
but from my perspective it is accurate. Here's what happened. I had a custom
subclass of NSView and I setup it up (in code) to be layer-backed with a
CATransition for the "subviews" key (i.e. fade in/out animation f
