Sorry for the delay. I¹ve been inaccessible for reasons I won¹t get into. I have tried it without setting any layers in IB. I think you may be correct about the copies. Another thing I don¹t know is if each cell simply uses the prototype to draw in the correct location, or it it does actually make copies for each cell. I¹m hoping for the latter, because what I really want is an AVPlayerLayer. The view I¹ve been referring to is intended to by my own version of an AVPlayerView (which I wish they would provide in AVFoundation, similar to the bindable QTMovieView. I have filed an enhancement request.) If the copy does not handle the layer-hosted view in the prototype correctly, then I¹m screwed. I have also tried just adding the layer to the backing layer, without success. I think I¹ve about exhausted the options.
This collection is a bank of AVPlayer controls for all movies which currently appear in the presentation window, on a different screen, and I want a (hopefully) playing thumbnail by the controls for easy identification. I may have to settle for a starting image, which isn¹t very useful is the movies fade in from black. Another thing AVFoundation lacks is access to something like a poster frame. I may file a bug report and see what happens. I¹ve been filing bug reports right an left lately. Unfortunately, haven¹t been getting much response. On 12/2/12 8:32 PM, "Kyle Sluder" <[email protected]> wrote: > Well, it's probably not a good idea to turn on layer-backing for a view in nib > and then try to transform it into a layer-hosting view by assigning to its > layer property and then calling -setWantsLayer:YES. There's a chance that > NSView will say, "oh, my wantsLayer property is already yes; I'll just keep on > doing my thing" even though your intent was to remove AppKit's ownership of > your layer. > > To be honest, the difference between layer-backed and layer-hosting views is > still murky, though the situation has gotten slightly better with the 10.8 > AppKit release notes. I just want one document that explicitly describes > *precisely* what AppKit does and does not control in each case. :-/ > > I did just remember something, though: NSCollectionView copies its collection > items around in some sort of crazy way that was subtly changed with the > introduction of NSViewController. Is it possible that the views in your > collection view are *NOT* the same instances that were unarchived from nib, > but rather *copies* of those views created by sending -encodeWithCoder: to the > collection item's view? > > --Kyle Sluder > >> _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
