
This file contains information about:
REPTW : Report Writer Graphics                    

******** THREADS2.DBF, 2.0 BETA MESSAGES ********

Msg#:  11731   Date:  22-Apr-91
Fm: Joe Gotthelf [DSA] 74017,3670
To: Jim McKinney 75140,2217 (X)

Draw one big box.
Draw another box that starts on the top of the big box, and ends on
the bottom of the big box. (do they actually overlap at the top and
bottom). then group them.

Msg#:  13713   Date:  30-Apr-91
Fm: Jackie Jaynes [Sysop] 76177,2777
To: Philip Steele 73155,1655 (X)

Philip,

This is not a bug.  The problem is that you are using CHR(195) and
CHR(180) to draw the boundaries of the box.  So when you use CHR(196),
which is a (-), and you say REPLICATE(CHR(196),22) it does not have
enough space on the right side to draw the 22nd character, if you do
23 characters, it overlaps the border.  My only suggestion is to
experiment with some other ASCII characters to draw the boundaries of
the box.  BTW,  it works the same way in FoxPro 1.02.

If you do not understand, let me know, and I will try and explain it
more thoroughly.

Jackie


******** THD201.DBF ********
Msg#:  106511   Date:  03-Jun-91
Fm: Etienne Muson 72745,1307
To: Nancy Jacobsen 72230,2664 (X)

Nancy:

It isn't hard, and you dont need to know HEX. The shareware file
HEXEDIT shows both the HEX, and ASCII data, and lets you edit either.

When you use Hijack, or some other program to create a PCL print file,
they naturaly assume that you are going to send the file to the
printer. Because of this you will usually find the laser reset command
in the very beginning of the file. This is ESC-E which in ASCII will
look like an arrow pointing to the left, and an E. They usually add a
formfeed (DEC-12) at the end of the file. In ASCII this looks like a
cross with a circle on top.

all of the codes mentioned above need to be removed. In HEXEDIT, or
comething similar, simply replace these codes with 00 (hex) which is
NUL.

Once this is done, you have a PCL file ready to be made into an
overlay macro.

If you would like my overlay-macro-make utility, I will send it up.
-Etienne.


******** THD202.DBF ********
Msg#:  146086   Date:  09-Sep-91
Fm: JAMES TERRY 71160,1261
To: all

I want to print a scanned image (.TIF or .PCX file) as part of a text
printout on a laser.  I have the image scanned in (acctually, it is a
signiture), and I want to print it (i.e. at lineno(), 5 say .... or
whatever).  If possible, how about INCLUDING it with a line of text -
such as a graph on a Word Perfect Document?  Any ideas?? Thanks.   -
jjt

Msg#:  146481   Date:  10-Sep-91
Fm: Andy Griebel [Plaid] 71441,3452
To: JAMES TERRY 71160,1261 (X)

James,

If you don't want the signature to "float" it's easy. Use a program
like arts & letters to PRINT TO FILE the tiff. Then, APPEND MEMO
picdata FROM thefile.prn to store the image in a FoxPro memo file.
When you're ready to print it, COPY MEMO picdata TO afile.txt, then
RUN COPY/B afile.txt PRN. You'll probably want to strip some leading
and trailing control characters from the print file (usually programs
will issue resets and form feeds you don't really want since FP will
be sending those)

IF you need the signature to float, you'll have to write a routine to
identify all of the x and y coordinates in the print file, and replace
them with the offset you need...kinda a PITA. There may indeed be
other ways. Menachem has played with this I think.

 Andy


Msg#:  147497   Date:  12-Sep-91
Fm: Andy Griebel [Plaid] 71441,3452
To: JAMES TERRY 71160,1261 (X)

By float I mean having the graphic appear in a position relative to
variable text. The method I described works only if you want the
graphic to be in the same place on the page every time. So, if you're
placing a signature on a letter where the body is the same length all
the time, fine. If the body changes (number of lines) from letter to
letter, then you've got a problem. The graphic is positioned by x,y
coordinates inside the print file itself...you can open it up and see
them. You could write a routine to replace them with the values you
wanted, but it would probably not be real speedy (depending on how
complex the graphic was). There may be an easier way to do that... Let
me know if you find out.
 Andy



******** THD203.DBF ********
Msg#:  180911   Date:  21-Nov-91
Fm: Cathy Selhorst [Fox] 76177,3002
To: Lisa Slater 72077,2417

Lisa, Enrique, and Glenn,

We think we have found the problem with printing the boxes to a file
and then printing that file later.  The way FoxPro handles how it
outputs the line characters changed awhile back in order to correctly
output joined boxes. This behavior appears to have changed how you
would print boxes from a file.
I assume you are selecting Print from the File menu when you go about
printing the file, correct?  This will put a carriage return and line
feed at the end of every "line".  When FoxPro outputs the boxes, it
handles joined boxes by outputting only the carriage return and spaces
over to the correct column to put in the joined box character. So,
when printing from the File menu, you are distorting the output you
received from the report.

The answer?  Instead of printing a "File" in the Print Dialog, choose
"ASCII file".  This will tell FoxPro that everything is fine in this
file and that it doesn't need any formatting done to it.  Or, you
could print it outside of FoxPro.

I hope this helps out!



Msg#:  181045   Date:  21-Nov-91
Fm: Lisa Slater 72077,2417
To: Cathy Selhorst [Fox] 76177,3002

Hi Cathy,

Actually I wasn't printing the file at all, whether by the File or
ASCII File method.

I was simply doing a MODI COMM the_file after I had sent the report to
a file, to allow a sophisticated Preview (i.e. scroll up as well as
down, do a Ctrl-F, etc.)  So nothing I did directly "distorted" the
output at all.

Now that I understand how FoxPro outputs the boxes, I see what was
going wrong. I really thought grouping boxes changed the output
characters to the joining chars in some magic sort of way, the way
they are changed in the Preview.  But now that I see your "underneath"
solution, I'm not sure there *is* a remedy for me... is there?

>L<


Msg#:  183913   Date:  28-Nov-91
Fm: Lisa Slater 72077,2417
To: Perot Systems 70720,2045

You can do this one of two ways.  If you have multiple detail lines,
as you appear to, and you want the bar to extend between records, you
should be using a vertical line created from a single-column box
object, and then telling this object to float.  It will become longer
to fit your detail band.  To get it to extend between records (you
must have a group footer or header band) you simply extend the box
into that band.

Subtle little trick <g>:  don't extend the box into the group header
or footer band until *after* you tell the box to float or you won't
get the "float" option.  However, it'll work properly if you do it in
the right order....
If you *don't* have multiple detail lines, I'll have to explain the
alternative when I get back next week.  You'll have to remind me what
the problem is <g>.

>L<


******** THD205.DBF ********
Msg#:  202732   Date:  13-Jan-92
Fm: Lisa Slater 72077,2417
To: Tamar E. Granor 73227,3303 (X)

Tamar,

The problem you are seeing has to do with the way Fox creates the
joined boxes.  It looks as if they replace one graphics character with
another to create that corner character but it ain't so <s>.  They
overlay characters, using a CR without a LF to go back and put the
other chars on top. I don't know how they trick the PREVIEW and the
Layout window into showing it differently.

The way it looks on the screen is not really important; and once you
get your symbol set corrected on your printer it will come out okay on
the printer because of the CR.  However, you will still have a problem
if you REPORT FORM to a file and then try to send the file to the
printer.  The only way I know to do this and get the boxes to behave
is to COPY FILE filename TO PRN. (You may have to SET SAFETY OFF and
use some other sundry tricks, like error trapping, to prevent a couple
of silly messages.)  Nancy checked this for me today and you can't do
it with TYPE, unfortunately.  And nobody in their right mind wants to
do a RUN COPY /B <g>...

>L<

Msg#:  210225   Date:  28-Jan-92
Fm: Calvin Hsia 72251,1725
To: Mike Dwyer 76100,3126 (X)

Hi Mike!

Isn't it fun to solve your own problems??

Anyway, to print without using the Extended ASCII chars for boxes and
lines, check out the report writer:  draw a box, then hit <enter> on
the box, choose Character, and they'll be done with normal (lower 128)
ASCII chars.
BTW, that's pretty crude!!
