That's how I read it, just wondered if anyone had done any real performance comparisions - my test is fairly simple.
M > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Meinte van't Kruis > Sent: 16 August 2006 10:43 > To: Flashcoders mailing list > Subject: Re: [Flashcoders] AS3 bitmapdata lock/unlock > > from the AS3 reference: > " > Locks an image so that any objects that reference the > BitmapData object, such as Bitmap objects, are not updated > when this BitmapData object changes. > To improve performance, use this method along with the > unlock() method before and after numerous calls to the > setPixel() or setPixel32() method. > " > > With this in mind, it does seem to function like a double > buffering mechanism, since you can actually alter bitmapdata > before showing it on screen, therefor avoidoing the image to > show while processing it. > > -Meinte _______________________________________________ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
