Thanks again Gary - but I looked into this by breaking at attempts to call
setDisplayNeeded on the view, with no luck. Can't find anything in my code that
is dirtying the view during the print draw.
However, another idea arises:
I am using this method to obtain the current CGContext during all
Definitely follow that train. Doing things with the wrong context is
definitely one possibility. By the way, the setNeedsDisplay doesn’t need to
happen on that view; it could be a subview, and there could be some other
operation that implicitly causes such a dirtying—remember, there’s also
I remembered seeing something like that in an app that had been doing some
things deep with the drawRect: call that was causing the view to become dirty
again. I fixed it by getting rid of that code. Try looking for something like
that first.
--
Gary L. Wade (Sent from my iPhone)
p.s. As I was unclear: the image returns YES to flipped and draws on that
assumption, looking good. When I say the image in the print dialog is "flipped"
I mean that it is backwards - mirrored - the reverse of what it should be - as
if it were an unflipped view - until it is drawn a second
I'm printing from a view-based OSX app (compiled for 10.11), and have found it
easy to print by creating a print operation from the view in question. The view
is flipped (that is, returns YES to IsFlipped) and looks good on screen. The
view creates a print operation this way:
