WYSIWYG is Wonky!

J. Landman Gay jacque at hyperactivesw.com
Tue Dec 17 14:51:09 EST 2013

On 12/17/13 1:30 PM, Marty Knapp wrote:
> 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.

That's why I move my printing to a hidden printing stack that is used 
only for that purpose. But even if you aren't printing reports, you 
might still be able to just copy everything to a printing stack.

> 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?

Some printers store their own copies of common fonts and they use those 
instead of the ones from the computer. It speeds up printing. If you are 
using a font the printer doesn't have, then it downloads the font from 
the computer.

> If I were to just leave formatForPrinting
> set to true all the time would that have any drawbacks other than
> display anomalies?

Editing becomes difficult. The insertion point isn't always accurate and 
font metrics can be way off in some cases. Text wrap gets wonky. What 
the user sees won't be what gets printed.

Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com

More information about the Use-livecode mailing list