Iceberg-Dev wrote: >> When working with NSBitmapImageRep, calling -bitmapData is a signal >> that you may be editing the data. It is not repackaged until the >> bitmap is drawn, or somesuch. It's illegal to just stash a pointer >> to the data and use it arbitrarily later - that won't necessarily >> be the same data as now backs the image. This is described in the >> 10.6 AppKit release notes. > > Calling -bitmapData works on Mac OS X 10.5, it does not work on Mac > OS X 10.6. On 10.6, it's slow and the data gets zeroed. Bug?
It would seem, but where is uncertain. I just threw something together to access every byte of a 3MPixel image sequentially. It consistently took just over 0.02s and did not result in data loss. _______________________________________________ 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 arch...@mail-archive.com
