Re: Why does this leak memory?
Re: Why does this leak memory?
- Subject: Re: Why does this leak memory?
- From: Jamie Curmi <email@hidden>
- Date: Sun, 19 Jan 2003 14:27:21 +1100
Thank you Joar, this works fine. Much appreciated.
I guess I should log a bug report about the memory leak when making a
copy though. It really does seem to occur.
Jamie
On Sunday, January 19, 2003, at 12:10 PM, j o a r wrote:
You could still get away with using only two images, call them
"originalImage" and "displayImage". Every time you need to update the
image, *composit* originalImage into displayImage and then add the
updated numbers.
Even if there is a memory leak (which I still don't quite believe), it
would hardly matter if you were to use just two images.
j o a r
On Sunday, Jan 19, 2003, at 02:04 Europe/Stockholm, Jamie Curmi wrote:
This is a good idea, and one that I toyed with. But if the image
under the numbers is complicated, not a solid colour, then this is
much more difficult. You need to somehow fill in the drawn in to
part with the original image - hence the use of copy.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.