More on Windows printing...
jerry at daniels-mara.com
Thu Jan 6 17:28:54 CST 2005
I checked the docs one last time and discovered that nausea and
dizziness are not among the side effects of using formatForPrinting.
On Jan 6, 2005, at 5:22 PM, Jerry Daniels wrote:
> This comment may account for the anomalous behavior you encountered
> (again, from Rev Docs):
> Important! Fonts inherited from another stack are not updated when
> you set the formatForPrinting of a stack. If the stack will be
> printed, make sure that either the stack's textFont property is set to
> a font name (not set to empty), or all fields to be printed have their
> own font rather than inheriting it.
> If the stack's formatForPrinting property is true, the setting of the
> windowBoundingRect property is ignored when the stack is opened or
> On Jan 6, 2005, at 5:11 PM, Lynch, Jonathan wrote:
>> I just tried it, and it was different. Maybe it depends on the font or
>> -----Original Message-----
>> From: use-revolution-bounces at lists.runrev.com
>> [mailto:use-revolution-bounces at lists.runrev.com] On Behalf Of Jerry
>> Sent: Thursday, January 06, 2005 6:10 PM
>> To: chipp at chipp.com; How to use Revolution
>> Subject: Re: More on Windows printing...
>> It's not the answer to world peace, but formatForPrinting property
>> keeps the fonts consistent looking between printer and screen on
>> Windows...at least it did with Rev 2.2. Haven't had to try it with
>> On Jan 6, 2005, at 4:48 PM, Chipp Walters wrote:
> use-revolution mailing list
> use-revolution at lists.runrev.com
More information about the use-livecode