on Fri, 27 Jul 2001 11:26:10 Scott Raney <[EMAIL PROTECTED]> wrote
>
> On Thu, 26 Jul 2001 Jacqueline Landman Gay <[EMAIL PROTECTED]> wrote:
>
>> I am using a simple "print this card" command to get a printout of a
>> card comprised of several text fields. Some of the text comes out
>> looking "overprinted" -- that is, within a rectangular area near the
>> center of the card it looks like the text was printed twice, the second
>> time with a 1-pixel offset. That part of the text looks blurry and bold,
>> and is illegible. The double printing within this imaginary rectangle
>> isn't related to any of the field rects, hidden or otherwise, and can
>> start anywhere, even at the center of a character in a line of text.
>> This happens whether formatForPrinting is set to true or false. The font
>> is Times 12, which is installed on the Mac. Printcolors is set to false
>> to avoid the gray background problem. The problem occurs in tests using
>> three different print drivers.
>>
>> Has anyone seen this before, and what causes it?
>
> Most likely a transparent image overlaps the text. In order to get
> the background color/pattern of these things right when printing
> (printing of transparent images isn't supported by the printer drivers
> on any platform), it actually takes a snapshot of the rect on screen.
> If any text is in that rect, it's grabbed at screen resolution. But
> then that text will be drawn again at printer resolution, hence the
> "double exposure" effect.
>
Nope. Can't be that here with me. Although the card contains a gif with a
transparent background, it definitely *does not* overlap the text.
My ultimate solution was to quit MC, shut down the computer, and start over.
If I printed without doing *any* editing in the stack, things were OK.
Otherwise it was iffy.
And I still don't know why telling a substack to open, print, and close (or
to print w/out opening for that matter), would cause such printer errors as
I get.
As I noted, Scott, MC is great, and I love it. But the print capabilities
need work.
> The best workaround is just to not use transparent images on stuff you
> will be printing. If you have to allow for them, you could hide the
> objects with text, do your own "import snapshot from rect" to grab an
> opaque image, delete or hide the original, then show the text objects
> again before printing.
> Regards,
> Scott
>
Sounds like a lot of work for something that should be as easy as "print
this card". But would this work for, say, cards that have to be odd sized
and outside the screenrect in order to print full pages?
Raymond
>> --
>> Jacqueline Landman Gay | [EMAIL PROTECTED]
>> HyperActive Software | 612-724-1596
>> Custom hypermedia solutions | http://www.hyperactivesw.com
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
