On 02/09/2013, at 4:45 PM, Fritz Anderson <anderson.fr...@gmail.com> wrote:

> On Sep 2, 2013, at 8:35 AM, Graham Cox <graham....@bigpond.com> wrote:
>> Creating a new one. It's not lagging, it always reports the pixel size, 
>> ignoring dpi and therefore actual size.
> 
> I think you are reporting a mere fact, not an anomaly. It's always been 
> pixels and it's too late to change. The rest is TL;DR.


I agree, I'm reporting a fact. The question I suppose is whether it's the 
expected thing. In many respects I think it probably *is* the expected thing, 
but some users are suggesting our app may be at fault because the image size 
they get isn't what they expected. There's no doubt about it being what has 
been done historically, but now that pixels are becoming somewhat divorced from 
image dimensions, it could be time for a change.

Our app can export images at pretty much any size and dpi, no matter what the 
size of the source image. The dpi and scale factors are used to figure out how 
many pixels that is, and we render to a bitmap of that size and write it out in 
the desired format, setting the dpi metadata correctly. The trouble is, that if 
we told the user we're exporting a 128 x 128 image at 144dpi, but then the 
Finder goes and displays that file with a 256 x 256 dimension, the user thinks 
we made a mistake and our export feature is faulty.

Maybe more education is needed but we thought we had explained all that. Maybe 
we need to display the calculated pixel sizes up front so the user doesn't get 
surprised by the outcome.

> Anyway, while the usage you hope for is understandable, so is Apple's choice 
> not to change it.

Totally ;)

--Graham
_______________________________________________

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to