Re:
On Dec 7, 2005, at 2:42 PM, Nick Nallick wrote:
I've been comparing the debug log generated by my app when it fails
to print and that generated by Preview when it succeeds in printing
the PDF generated from the same job. Specifically I've been
looking at the setup instructions to see if Preview is asking for
something different than I am. Apart from the exact order of
things and the file IDs there are only a few differences.
The Canon settings show a difference in BJPrintQuality and
BJDitherPattern. The only thing I can think of that might account
for this is that I'm setting the interpolation quality of the CG
context used for printing before I draw into it:
I don't think the interpolation quality has anything to do with it or
the other keys I've omitted in my quoting of your message above.
Since the error (that you described in your earlier message) that is
happening is coming from the Canon driver, I strongly suspect it is
the Canon specific setting. Why it is different when printing from
your app vs Preview is mysterious to me, other than things I've
suggested before, that is, saved print settings, and so forth.
Does any of this seem like it might be reason for my job to fail?
Yes, I can imagine that if the Canon driver gets a setting that
doesn't make sense to it, it could complain and fail. That isn't good
behavior but some of the drivers do things like this. Why your app is
generating a different value than Preview seems likely to some old
data that is being cached by someone or something: either a saved
print setting you are reusing or a printing preset.
David
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Printing mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/printing/email@hidden
