Hi Quincey,
> On Jan 15, 2016, at 11:24 , Andreas Höschler <ahoe...@smartsoft.de
> <mailto:ahoe...@smartsoft.de>> wrote:
>>
>> However, I generated the image rep with a 851 x 899 view and wrote it into a
>> PNG file (code in earlier mail).
>
> Yes, I saw, but you didn’t include (or I couldn't find) the log output that
> showed the size of the NSImage object, even though you had a line of code to
> log it.
15/01/16 21:03:29,842 SOSmartBrowser[56701]: image <NSImage 0x7fb35c30
Size={698, 782} Reps=(
"NSBitmapImageRep 0x7fb18de0 Size={698, 782} ColorSpace=(not yet loaded)
BPS=8 BPP=(not yet loaded) Pixels=1396x1564 Alpha=YES Planar=NO Format=(not yet
loaded) CurrentBacking=nil (faulting) CGImageSource=0x81d92150"
)>
> NSImage, when given image data that has A x B pixels and a PPI (pixels per
> inch) of C, may choose to ignore C, rather than use it to compute C x D
> points. It’s not clear whether this happened in your case or not.
>
> It does this because PPI is often just wrong. The actual pixel dimensions are
> the only reliable numbers.
>
> Same thing. Preview doesn’t believe any metadata about the image size. It
> just works with the pixels.
Good enough for me! It's just important to note that NSScaleNone is no longer
an option due to the points/pixel discrepancy (this was no issue on earlier
systems). Not yet completely used to working with these high resolution
screens. :-)
Thanks,
Andreas
_______________________________________________
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
