I've been investigating a bug in our product when running on Leopard: our custom views inside NavServices panels weren't showing up. I tried downloading and building
http://developer.apple.com/samplecode/AddNibToNav/to see how it is supposed to be coded, and our product's code looked very similar. I guess the engineer who wrote our code had looked over the Apple sample before starting. Good. But in Apple's sample program, the accessory view controls show up fine on 10.5 9A466 (although the project requires changes to link succesfully; need to remove a foo.a file from the project). If our code was so similar, why was it not behaving the same way?
Then I started looking at the differences between our NIBs and the sample project NIBs and I noticed that our NIBs have the "Compositing" flag turned ON for the holder window that we pull the top level view out of. Apple's sample project does not have this flag set. Sure enough, when I turn the Compositing flag off in our NIBs the controls appear correctly and when I turn the flag on in the Apple sample project, most (but not all) of the controls fail to display properly.
So...
Is this an undocumented requirement (NIB's used to hoist a view hierarchy into a NavServices custom dialog must not have the Compositing attribute set), or is this a bug in pre-release Leopard? Its definitely a change in behavior from Tiger (but some of these are bound to occur when swapping out an implementation).
--
Tim Gogolin
Adobe Systems
