On Jun 8, 2010, at 2:02 PM, Matej Bukovinski <[email protected]> wrote:
> Could you perhaps elaborate a bit how you think that a layer backed view > could help? Layers are composed into their own backing stores, so you can accumulate data there rather than recalculating it every time you need to repaint. That said, you would need to use a layer hosting view rather than a layer backed view, which might put you at a disadvantage from where you started. > > The window overlay sounds like it could work. Hoverer, a NSView overlay would > be preferred since I'm inserting the overlay in the WebView's scroll view > (and matching the documents view size via bounds change notifications). This > works very well when scrolling both the web and overlay view at the same time > (and is also efficient). I don't believe you're actually allowed to mess with the web view's scroll view hierarchy; the web view comes with a prepackaged scroll view, unlike say NSTextView. It sounds like the overlay window is the best bet. --Kyle Sluder (Sent from WWDC)_______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
