site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=Be7CL9lb2RZR+V/jOFRtAKkIgjEf3G8Irt1EkUEnhus=; b=PLeqjX2LsmATWmQDsEz1WKg8EC2N4iYUBNagGixQzrECurVB5gJ5Ul0+mrBK1EnrjG SMjUyNc8ATkBlsDiysjImxUXX+CmoQap37x8jYPVnB5NGoROuvQQmL3bLUGn86mcwGuB vzaE5al0On67GoTEcIMsdKA6t0cJFoJ3BIOEo= Hi Darrin I'm not actually wanting to change the width or height though, I'm just getting the value, which is why I was puzzled why the warning was shown. I've since discovered that using [outputImage width] rather than outputImage.width dot syntax does not throw up the warning. Martin Baker www.digital-heaven.co.uk www.twitter.com/digitalheaven www.videospaceonline.com www.finalcutters.com ------------------------------------------------------ Digital Heaven Ltd is registered in England and Wales Company registration number: 3628396 Registered address: 55 Lynwood Drive, Worcester Park, Surrey KT4 7AE VAT registration number: GB 736 0989 03 On 1 Aug 2011, at 18:34, Darrin Cardani wrote:
Martin,
It's because FxImages are mostly immutable. There's no safe way to change the image data in an FxImage, so we deprecated the setters and updated the initializers to make it more clear. In the past, when a plug-in called -setWidth:, the image's width member variable would be changed, but the data behind it wouldn't. (Because how can we know if you want to scale or crop it when changing the width.) So the object was then in an inconsistent state and any operations on it were inherently unsafe (at least with bitmaps where reading or writing off the edge could clobber other parts of memory).
Also, it allowed the plug-in to do some unsafe things like changing an output image's bitmap pointer behind the app's back. If that happens, the app no longer knows if the bitmap owns the data pointer or not, so it can't safely free it.
So if you want to change the width or height of an image you now have to create a new image. This shouldn't be a performance hit because you have to regenerate the data, anyway. Creating a new FxImage is a pretty fast operation with the new initializers.
Note that I said they're "mostly" immutable. It is fairly safe to change the field value, for example, since it doesn't require changing the image data. It's rare that you'd want to change that value. But you could, theoretically, create a new image that you're using as an intermediate buffer, and set the field value to match something the app passed you, or something like that. Not a common case, but much less problematic than changing the width or height.
Darrin
On Jul 30, 2011, at 1:48 AM, Martin Baker wrote:
Everytime I call FxImage.width, Xcode throws up a warning that "setWidth is deprecated". Why?
Martin Baker www.digital-heaven.co.uk www.twitter.com/digitalheaven www.videospaceonline.com www.finalcutters.com ------------------------------------------------------ Digital Heaven Ltd is registered in England and Wales Company registration number: 3628396 Registered address: 55 Lynwood Drive, Worcester Park, Surrey KT4 7AE VAT registration number: GB 736 0989 03
_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com
This email sent to dcardani@apple.com
-- Darrin Cardani dcardani@apple.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... This email sent to site_archiver@lists.apple.com