Hi all:
good night.
I think that I posted this message in another group, where I had not support.
Can somebody tell me why the attached program only prints 63 lines in a page?
It stays a large margin in the bottom. This margin is greater then the one returned by
oPrint:paperSize().
Also the oPrint:setViewPort() returns the view port size in pixels (I suppose) and the 
XbpPresSpace() was built for using for the coordinate system units GRA_PU_LOMETRIC
I'm using a HP DeskJet 5550.
The program may be compiled using xpp testprt -a-m-n-q-w-wu-b /link:"/pm:pm /de"

Beling
TIA

hi,

> Can somebody tell me why the attached program only prints 63 lines in a
> page?
i can print 68 lines on a Kyocera 1010 with your Application

> It stays a large margin in the bottom. This margin is greater then the one
> returned by
> oPrint:paperSize().
at bottom there is allways a "not printable" Area

> Also the oPrint:setViewPort() returns the view port size in pixels (I
> suppose) and the
> XbpPresSpace() was built for using for the coordinate system units
> GRA_PU_LOMETRIC
> I'm using a HP DeskJet 5550.
it is your Inkjet. try same Code on a Laser Printer and get 68 lines

> The program may be compiled using xpp testprt -a-m-n-q-w-wu-b
> /link:"/pm:pm /de"
i did not know that that i can use "xpp" with "/link" in one line, great !

greetings by OHR
Jimmy

Hi AUGE_OHR:
good morning.
Many thanks.
Please see some notes below.

Beling
Best regards.

AUGE_OHR escreveu:
> hi,
> 
>> Can somebody tell me why the attached program only prints 63 lines in a
>> page?
> i can print 68 lines on a Kyocera 1010 with your Application
> 
Good to know that it may be a printer question. I can only print the same amount of lines 
using PCL 5.
>> It stays a large margin in the bottom. This margin is greater then the one
>> returned by
>> oPrint:paperSize().
> at bottom there is allways a "not printable" Area
The problem is that the "not printable" area is greater than the one returned by the 
XbpPrinter:paperSize()
> 
>> Also the oPrint:setViewPort() returns the view port size in pixels (I
>> suppose) and the
>> XbpPresSpace() was built for using for the coordinate system units
>> GRA_PU_LOMETRIC
>> I'm using a HP DeskJet 5550.
> it is your Inkjet. try same Code on a Laser Printer and get 68 lines
Do you know why the "not printable" returned by :paperSize() does not match with that I 
can really print? :paperSize() must not return the real "not printable" area?
> 
>> The program may be compiled using xpp testprt -a-m-n-q-w-wu-b
>> /link:"/pm:pm /de"
> i did not know that that i can use "xpp" with "/link" in one line, great !
Good to know I could be useful.
> 
> greetings by OHR
> Jimmy
Greetings Jimmy
> 
> 
>

Beling,

A few years ago I was having trouble with a particular HP printer don't
recall which one but, "HP DeskJet 5550" is vaguely familiar.

   >don<

On Thu, 22 Nov 2007 11:57:48 -0200, Carlos Beling wrote:

> Hi AUGE_OHR:
> good morning.
> Many thanks.
> Please see some notes below.
> 
> Beling
> Best regards.
> 
> AUGE_OHR escreveu:
>> hi,
>> 
>>> Can somebody tell me why the attached program only prints 63 lines in a
>>> page?
>> i can print 68 lines on a Kyocera 1010 with your Application
>> 
> Good to know that it may be a printer question. I can only print the same amount of lines 
> using PCL 5.
>>> It stays a large margin in the bottom. This margin is greater then the one
>>> returned by
>>> oPrint:paperSize().
>> at bottom there is allways a "not printable" Area
> The problem is that the "not printable" area is greater than the one returned by the 
> XbpPrinter:paperSize()
>> 
>>> Also the oPrint:setViewPort() returns the view port size in pixels (I
>>> suppose) and the
>>> XbpPresSpace() was built for using for the coordinate system units
>>> GRA_PU_LOMETRIC
>>> I'm using a HP DeskJet 5550.
>> it is your Inkjet. try same Code on a Laser Printer and get 68 lines
> Do you know why the "not printable" returned by :paperSize() does not match with that I 
> can really print? :paperSize() must not return the real "not printable" area?
>> 
>>> The program may be compiled using xpp testprt -a-m-n-q-w-wu-b
>>> /link:"/pm:pm /de"
>> i did not know that that i can use "xpp" with "/link" in one line, great !
> Good to know I could be useful.
>> 
>> greetings by OHR
>> Jimmy
> Greetings Jimmy
>> 
>> 
>>

Hi Don:
good night.
Many thanks.
I finished convincing myself that printers are as pleasant as dentist probes are.

Beling
Best regards

Donald R. Keating escreveu:
> Beling,
> 
> A few years ago I was having trouble with a particular HP printer don't
> recall which one but, "HP DeskJet 5550" is vaguely familiar.
> 
>    >don<
> 
> On Thu, 22 Nov 2007 11:57:48 -0200, Carlos Beling wrote:
> 
>> Hi AUGE_OHR:
>> good morning.
>> Many thanks.
>> Please see some notes below.
>>
>> Beling
>> Best regards.
>>
>> AUGE_OHR escreveu:
>>> hi,
>>>
>>>> Can somebody tell me why the attached program only prints 63 lines in a
>>>> page?
>>> i can print 68 lines on a Kyocera 1010 with your Application
>>>
>> Good to know that it may be a printer question. I can only print the same amount of lines 
>> using PCL 5.
>>>> It stays a large margin in the bottom. This margin is greater then the one
>>>> returned by
>>>> oPrint:paperSize().
>>> at bottom there is allways a "not printable" Area
>> The problem is that the "not printable" area is greater than the one returned by the 
>> XbpPrinter:paperSize()
>>>> Also the oPrint:setViewPort() returns the view port size in pixels (I
>>>> suppose) and the
>>>> XbpPresSpace() was built for using for the coordinate system units
>>>> GRA_PU_LOMETRIC
>>>> I'm using a HP DeskJet 5550.
>>> it is your Inkjet. try same Code on a Laser Printer and get 68 lines
>> Do you know why the "not printable" returned by :paperSize() does not match with that I 
>> can really print? :paperSize() must not return the real "not printable" area?
>>>> The program may be compiled using xpp testprt -a-m-n-q-w-wu-b
>>>> /link:"/pm:pm /de"
>>> i did not know that that i can use "xpp" with "/link" in one line, great !
>> Good to know I could be useful.
>>> greetings by OHR
>>> Jimmy
>> Greetings Jimmy
>>>
>>>

On Thu, 22 Nov 2007 11:57:48 -0200, Carlos Beling
<beling@itevip.com.br> wrote:

>The problem is that the "not printable" area is greater than the one returned by the 
>XbpPrinter:paperSize()

>Do you know why the "not printable" returned by :paperSize() does not match with that I 
>can really print? :paperSize() must not return the real "not printable" area?

I remember the unpleasant discovery, back when I was first developing
the Top-Down printer class in 2000, that some printer drivers return
inaccurate :papersize() information.  But it has been years since I
heard any of those reports.  Perhaps downloading a newer driver for
that printer will solve it.

Regards,
Clayton

Clayton Jones   www.cjcom.net 
 Top-Down Library for Xbase++
 X-DBU Database Utility   
 X-MEMO Memo Field Replacement

Hi Clayton

Can you remember if it was consistent every time, or it gave the error 
only some times ?

Regards

Clayton Jones wrote:
> On Thu, 22 Nov 2007 11:57:48 -0200, Carlos Beling
> <beling@itevip.com.br> wrote:
> 
>> The problem is that the "not printable" area is greater than the one returned by the 
>> XbpPrinter:paperSize()
> 
>> Do you know why the "not printable" returned by :paperSize() does not match with that I 
>> can really print? :paperSize() must not return the real "not printable" area?
> 
> I remember the unpleasant discovery, back when I was first developing
> the Top-Down printer class in 2000, that some printer drivers return
> inaccurate :papersize() information.  But it has been years since I
> heard any of those reports.  Perhaps downloading a newer driver for
> that printer will solve it.
> 
> Regards,
> Clayton
> 
> Clayton Jones   www.cjcom.net 
>  Top-Down Library for Xbase++
>  X-DBU Database Utility   
>  X-MEMO Memo Field Replacement

Hello Johan,

>Can you remember if it was consistent every time, or it gave the error 
>only some times ?

Sorry, I don't know.  The issues came up when I first released the TD
printer class which had tested ok with the printers I was using at the
time.  I occasionally recived a problem report from someone using
another printer.  I remember that we finally deduced that it had to be
caused by faulty driver-returned metrics.  I do remember some cases
where downloading new drivers solved the problem (according to follow
up reports - I was never directly involved).  It was not a widespread
problem.  It may have been two or three reports over a couple of
years.  

There were other driver related problems as well (besides :papersize()
metrics), but over time they all faded away.  It's been over six years
now.  I assumed that the printer companies' programmers had gradually
worked out the bugs.  That's why I suggested trying a different driver
- perhaps it's an old one.  Sorry I don't have anything more concrete
than that.


Regards,
Clayton

Clayton Jones   www.cjcom.net 
 Top-Down Library for Xbase++
 X-DBU Database Utility   
 X-MEMO Memo Field Replacement

Hi Clayton:
good morning. It's always good heard you.
Many thanks.
I downloaded the new driver. The paper size is ok.
There are two problems (in my thinkings):
. the :viewPort() seems to be returned in pixels
. the printer does not print in the :paperSize() area.

Beling
Greetings

Clayton Jones escreveu:
> On Thu, 22 Nov 2007 11:57:48 -0200, Carlos Beling
> <beling@itevip.com.br> wrote:
> 
>> The problem is that the "not printable" area is greater than the one returned by the 
>> XbpPrinter:paperSize()
> 
>> Do you know why the "not printable" returned by :paperSize() does not match with that I 
>> can really print? :paperSize() must not return the real "not printable" area?
> 
> I remember the unpleasant discovery, back when I was first developing
> the Top-Down printer class in 2000, that some printer drivers return
> inaccurate :papersize() information.  But it has been years since I
> heard any of those reports.  Perhaps downloading a newer driver for
> that printer will solve it.
> 
> Regards,
> Clayton
> 
> Clayton Jones   www.cjcom.net 
>  Top-Down Library for Xbase++
>  X-DBU Database Utility   
>  X-MEMO Memo Field Replacement

Hello Carlos,

>I downloaded the new driver. The paper size is ok.
>There are two problems (in my thinkings):
>. the :viewPort() seems to be returned in pixels
>. the printer does not print in the :paperSize() area.

Ok, understood.  The main thing is to determine for sure whether the
problem is in your code or stems from either the driver or the
printer.  Have you tested your code with other printers, and with
different driver versions with the same printer?

Once you're certain it's not in your code...


Regards,
Clayton

Clayton Jones   www.cjcom.net 
 Top-Down Library for Xbase++
 X-DBU Database Utility   
 X-MEMO Memo Field Replacement

Hello Clayton:
good afternoon.
Thanks again.
I don't remember somebody tested the sample I attached in the first message and printed 71 
lines. I think it may be really a printer(s) driver(s) problem.

Beling
Best regards

Clayton Jones escreveu:
> Hello Carlos,
> 
>> I downloaded the new driver. The paper size is ok.
>> There are two problems (in my thinkings):
>> . the :viewPort() seems to be returned in pixels
>> . the printer does not print in the :paperSize() area.
> 
> Ok, understood.  The main thing is to determine for sure whether the
> problem is in your code or stems from either the driver or the
> printer.  Have you tested your code with other printers, and with
> different driver versions with the same printer?
> 
> Once you're certain it's not in your code...
> 
> 
> Regards,
> Clayton
> 
> Clayton Jones   www.cjcom.net 
>  Top-Down Library for Xbase++
>  X-DBU Database Utility   
>  X-MEMO Memo Field Replacement

Hi

I would agree to driver problems as well, since this does not seem to 
happen at other sites.  The interesting thing is we have tried a few 
other drivers, but there is a number of other variables that could cause 
problems as well such as printers connected directly to the server or 
connect to a printer box etc.  It gets hard to figure out where the 
problems lies, since software vendors always gets the blame.  But this 
should help narrow the problem a bit i think.

Thanx to the help.

Carlos Beling wrote:
> Hello Clayton:
> good afternoon.
> Thanks again.
> I don't remember somebody tested the sample I attached in the first 
> message and printed 71 lines. I think it may be really a printer(s) 
> driver(s) problem.
> 
> Beling
> Best regards
> 
> Clayton Jones escreveu:
>> Hello Carlos,
>>
>>> I downloaded the new driver. The paper size is ok.
>>> There are two problems (in my thinkings):
>>> . the :viewPort() seems to be returned in pixels
>>> . the printer does not print in the :paperSize() area.
>>
>> Ok, understood.  The main thing is to determine for sure whether the
>> problem is in your code or stems from either the driver or the
>> printer.  Have you tested your code with other printers, and with
>> different driver versions with the same printer?
>>
>> Once you're certain it's not in your code...
>>
>>
>> Regards,
>> Clayton
>>
>> Clayton Jones   www.cjcom.net  Top-Down Library for Xbase++
>>  X-DBU Database Utility    X-MEMO Memo Field Replacement