Then maybe the solution is to change the fontname in _screen instead of
using the FONT clause?
I haven't tried it but it seems logical:
CLEAR
FOR N = 1 TO 4
lcSaveFontName = _screen.FONTNAME
_screen.FONTNAME = "WINGDINGS"
? CHR(0x6F)
_screen.FONTNAME = "ARIEL"
?? CHR(9)+'test' FONT "Ariel"
_screen.FONTNAME = lcSaveFontName
ENDFOR
Never mind, that didn't work but maybe I'm still on to something?
Hal Kaplan wrote:
=> -----Original Message-----
=> From: [EMAIL PROTECTED]
=> [mailto:[EMAIL PROTECTED] On Behalf Of Paul Newton
=> Sent: Monday, October 02, 2006 11:41
=> To: [email protected]
=> Subject: Re: ? and ??
=>
=> Tx for the reply Hal
=>
=> From which and re-reading my post it seems that I may have
=> not made clear the problem which is NOT coordinating output
=> to printer/screen/console. The probel is the blank lines -
=> it so happens that the problem can be reproduced when
=> directing the ?/?? output to the screen and when directing
=> it to the printer. It's just easier to see and
=> test/reproduce when output is directed to the screen.
=>
Sorry for the misplaced jocularity, Paul.
Here is what I found.
The extra lines are caused by specifying a font that is different from
_screen.FontName
Get rid of the font clauses in your pgm and there are no blank lines.
Change the font clause to match your screen font and there are no blank lines.
I did not check the printer because all i have is a page printer and it's a
PITA.
I am using VFP 9SP1 and WinXPRO-SP2
HALinNY
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
