On Sun, Jan 07, 2001 at 10:44:14AM -0800, [EMAIL PROTECTED] wrote:
> > From [EMAIL PROTECTED] Fri Jan 5 17:53:07 2001
> > To: [EMAIL PROTECTED]
> > Subject: LPRng: pjl_ready_msg confusion
> > From: Jason L Tibbitts III <[EMAIL PROTECTED]>
> > Date: 05 Jan 2001 18:53:21 -0600
> >
> > In ifhp 3.4.4, set pjl_ready_msg to "Printing: \%s{n} \%s{J}" and
> > pjl_display_size to 32 for my HP 8100DN. I figured this would put the
> > obvious up on the screen, as it does with another host running a different
> > printer and older (slightly hacked[1]) version of ifhp. Instead, for the
> > duration of the job I get just the user name in the display while the job
> > is printing, then at the end I get the expected string for just a second
> > before "READY" reappears.
> >
> > I suppose that RDYMSG is supposed to control what's printed while the
> > printer is idle, but something (probably the pagecount code) is erasing
> > this. But what controls the display while the job is printing? And how
> > can I get a message to stay on the screen while the printer is idle?
> >
> > Thanks!
> >
> > 1) My slightly hacked version puts "Printing: user" while the job is
> > printing and "Last Job: user" while the printer is idle. I did this a
> > very long time ago, and that patch doesn't match up with current
> > versions.
> >
> > - J<
>
> It turns out that there are TWO (2) places where the DISPLAY is set.
> Try the following patch and see if this works:
I send in a patch which does nearly the same about a week ago (see
http://www.lrz-muenchen.de/services/netzdienste/email/email-archive/lprngAlprng.com/msg04211.html
Subject: LPRng: ifhp: pjl_console messages & printer status/debug output)
which does nearly the same with a common subroutine. The difference I see
is that Patricks patch is ignoring the length settings (Pjl_display_size).
As there are other places (I think the accounting parts) which uses PJL
JOB commands without the DISPLAY settings I think a common subroutine
which creates a string "DISPLAY="..."" (and nothing if console messages are
disabled) is a really nice thing (and even easier to maintain).
Just to mention the weak areas I know of my patch: Not multithreading save
(if this is ever needed...).
What are you thinking, Patrick ?
Regarding the comment of Jason to the wrong use of pjl_ready_msg: Completely
true, there should be used a pjl_busy_msg instead. But as I am not
familar with introducing options into the ifhp code I took the simplest
solution (In fact, before the introduction of pjl_ready_msg a patch
looked to complicated for me :-).
Again, thanks for any work on that field - the console messages are
a really nice thing... (also on the wishlist for this:
cutting of n last chars from a string)
Greetings
Hermann
--
Bildverarbeitungsgruppe des Interdiziplinaeren Zentrums fuer
wissenschaftliches Rechnen, Universitaet Heidelberg
INF 368; 69120 Heidelberg; Tel: (06221)54-8826, -6314 Fax: -8850
Email: [EMAIL PROTECTED]
-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
