mmm thanks for the info, I'm trying right now to draw directly in a
custom view... unfortunately I still get the same result... on average
each time I regenerate the preview the memory usage in Activity
monitor goes up by approx. 10mb (real memory), and never comes down...
at this rate it climbs pretty quickly...
Once again, MallocDebug doesn't show any leaks, neither does
Instruments... not sure what I am doing wrong...
On 3-Dec-08, at 1:33 AM, Rob Keniger wrote:
On 03/12/2008, at 1:53 PM, Jean-Nicolas Jolivet wrote:
since I already have a bitmapImageRep I figured displaying its data
in an NSImaveView was probably not a big loss in terms of
performance... I wonder if drawing directly would be worth it in my
case... and most importantly, if it would help solve my huge memory
problem (perhaps drawing directly instead of storing the preview in
an imageRep would help on the memory usage though so you might have
a point!)
I'd definitely try drawing directly, in my experience NSImageView
does quite a few funky things (probably for caching/performance
reasons) and generally if you're changing the image a lot it's best
to just draw directly in your own custom view.
--
Rob Keniger
_______________________________________________
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/silvertab%40videotron.ca
This email sent to [EMAIL PROTECTED]
Jean-Nicolas Jolivet
[EMAIL PROTECTED]
http://www.silverscripting.com
_______________________________________________
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]
