WYSIWYG is Wonky!

Marty Knapp martyknappster at gmail.com
Tue Dec 17 14:30:39 EST 2013


In my case setting formatForPrinting to true, saving, closing, reopening 
& printing is way too clunky. Then if a user has to make a correction . 
. .  For report-style printing that would be fine, but not for my use.

In my tests, setting formatForPrinting to true and then printing right 
away did work great for some fonts, but not others - all TrueType. I 
wonder what's up with that? If I were to just leave formatForPrinting 
set to true all the time would that have any drawbacks other than 
display anomalies?

This takes me back to printing on a PC in the mid 80s - fiddling with a 
word processing document trying to get it to print like you wanted! Then 
I bought my first Mac - an SE 30 and I didn't look back - well, till 
now. (And that 9" screen was to die for . . . not to mention that I had 
to sell my first-born son into slavery to afford it!)

I did file 3 bug reports yesterday, all printing related, and they've 
been confirmed. So maybe this will get fixed???

Marty
> On 12/16/13 2:30 PM, Marty Knapp wrote:
>
>> One thing I don't understand is that on Windows if I print with
>> formatForPrinting set to false, the fonts print very nicely and with
>> (seemingly) no less resolution than when you set formatForPrinting to
>> true. And they're TrueType fonts so I thought (obviously incorrectly)
>> that screen fonts and printer fonts were a thing of the past. It sure
>> seems like we ought to have WYSIWYG printing on Windows at this stage of
>> the game.
>
> As I understand it, the font file loads when the stack does. So if you 
> aren't closing and re-opening the stack then you aren't really using 
> the printer fonts and it would look the same as before.
>
> If I need to print reports, I usually designate a separate stack 
> that's used only for printing and set its formatForPrinting to true 
> during development. It doesn't affect anything on Mac, and it's always 
> set up for printer fonts on Windows when it opens. If you don't have a 
> printing stack, you have to close and re-open the main stack and 
> that's ugly.
>





More information about the Use-livecode mailing list