• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: [Leopard] bug in [NSGraphicsContext attributes]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Leopard] bug in [NSGraphicsContext attributes]


  • Subject: Re: [Leopard] bug in [NSGraphicsContext attributes]
  • From: Michael Monscheuer <email@hidden>
  • Date: Wed, 07 Nov 2007 14:58:00 +0100

Hi!

> This will not help if your goal is to distinguish between printing to
> a printer and printing to a PDF.

Right. We use -[NSGraphicsContext attributes] *and* -[NSGraphicsContext isDrawingToScreen]
on the current graphics context in -[NSView drawRect:] methods to distinguish between
screen, PDF, PS and manual bitmap contexts.

I filed a report (Bug ID# 5584898) with a simple example app attached.

I managed to find a workaround by (mis)using an existing hack in our app.
But I don't like hacks. Would feel better to be able to use the official API...

Michael

Ken Ferry schrieb:
Hi Michael,

Yes, please file a bug if something changed here.

Would -[NSGraphicsContext isDrawingToScreen] work for you?  It really
has more to do with whether the destination context is pixel-based
than with whether it's the screen.

"A return value of NO may mean that the drawing destination is a
printer, but the destination may also be a PDF or EPS file."

This will not help if your goal is to distinguish between printing to
a printer and printing to a PDF.

-Ken
Cocoa Frameworks

On Nov 6, 2007 5:02 AM, Michael Monscheuer <email@hidden> wrote:
Hi!

When creating an NSGraphicsContext using -graphicsContextWithGraphicsPort:flipped:
with a CGPDFContext as graphics port, the dictionary returned by -attributes
of the created NSGraphicsContext no longer contains the documented key-value pairs.

In Tiger the attribute dict contains keys like
NSGraphicsContextRepresentationFormatAttributeName and
NSGraphicsContextDestinationAttributeName.
In Leopard no more.

If you rely on these keys and values, I'd suggest to check your apps.

As this bug also affects possible analysis while printing:
Any ideas how to find out if current context's graphics port
(e.g. while printing a PDF via NSPrintPanel) is a PDF context or not?

Michael

P.S.: Yes, I will file a bug report for sure :-)

---
Michael Monscheuer
www.icalamus.net
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden




--
=======================================================
And refashioning the fashioned
lest it stiffen into iron
is work of endless vital activity.
[Goethe]

Michael Monscheuer
Askanierweg 5a
21465 Wentorf

Tel.:+49 40 72699442
Fax.:+49 40 72410664

mailto:email@hidden
mailto:email@hidden

http://www.icalamus.net

=======================================================
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden


References: 
 >[Leopard] bug in [NSGraphicsContext attributes] (From: Michael Monscheuer <email@hidden>)
 >Re: [Leopard] bug in [NSGraphicsContext attributes] (From: "Ken Ferry" <email@hidden>)

  • Prev by Date: Re: leopard malloc error
  • Next by Date: -[NSConditionLock unlockWithCondition:]: lock (<NSConditionLock: 0x59f2050> '(null)') unlocked when not locked
  • Previous by thread: Re: [Leopard] bug in [NSGraphicsContext attributes]
  • Next by thread: NSImage problem with universal binary
  • Index(es):
    • Date
    • Thread