![]() |
I looked at the BreakIntoLines procedure and played around changing the two 'show' commands from 'index sub 2' to 'index add 2' and that worked. I just read Alan's message and the suggestion of -93 vs 93 works also and is of course the better solution. The obvious thing I missed was the negative sign. Thanks Lee & Alan. -----Original Message----- From: Lee Howard [mailto:faxguy@deanox.com] Sent: May 11, 2001 2:25 PM To: Curtis Rempel; 'hylafax-users@hylafax.org' Subject: Re: [hylafax-users] BreakIntoLines goes the wrong direction? At 01:54 PM 5/11/01 -0600, Curtis Rempel wrote: >I've been playing around with a custom cover page on 4.1b3 for awhile now >and gave up on the BreakIntoCommentX procedure - the only thing I could get >it to do was print one long line of comments that ran off the page. >Looking at BreakIntoLines seemed to be the way to go. Out of the gate, it >works great, however, my comments go up the page instead of down the page. >That is, the first line of comments starts in the correct position but the >next line appears above the first line instead of below it and on it goes up >the page instead of down the page. > >Here's the PostScript I'm using: > >/linewidth 1783 def >/lineheight 93 def >/y 1517 def /x 300 def >linewidth lineheight x y comments BreakIntoLines > >I must be missing something obvious.... Yeah, postscript coordinates are in the 1st quadrant, so as you go down a page the y coordinate gets smaller, not bigger. You may want to take a look at: http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=81 If you can make the given patch use stringwidth rather than character-count, then we can probably get the patch committed to CVS. Thanks. Lee ____________________ HylaFAX(tm) Users Mailing List _______________________ To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null