|
From: James W. W. <ja...@fr...> - 2005-08-08 18:07:48
|
"Edward K. Chew" <ek...@lg...> wrote: >After trying this and that, it seems I have finally hit on a winning >recipe. I thought I could get away with allocating one large 11 x >17 @ 300 dpi buffer and rendering into it in tiles no larger than >2048 x 2048 pixels through careful manipulation of view ports and >pane rectangles, but no joy. Apparently, there is some kind of >limit to the absolute dimensions of the buffer, regardless of how >small a pane you are accessing within it. Should you exceed that >limit, you will see some psychedelic wraparound effects. ... >I think this buffer size limit is more sensitive to the horizontal >dimension. It only seems to come up when I print in landscape >orientation. This is all under Tiger, incidentally. With some >trepidation, I plan to test the same code under Panther today...wish >me luck! This sounds like a rowBytes limit, so it prompted me to search for rowBytes usage in Quesa. I found a bug in E3MacDrawContext.c, where it was directly reading the rowBytes field of a PixMapHandle instead of using GetPixRowBytes. I checked in a fix. So you might want to check that out, and try the big-buffer method again. -- James W. Walker, ScriptPerfection Enterprises, Inc. <http://www.write-brain.com/> |