#]Printer Driver
8 messages in this thread
Roy, how about making the timed black out an option. I don't want both the
clock and POPCLI.
No, I don't own a NEC P5XL but a NEC CP6.
-Joergen
I have been thinking about it. maybe on startup you can determine the number
of minutes before the backdrop (i.e. BACKDROP 3 – for a three minute wait, and
BACKDROP 0 for no timed forced backdrop). Since I don't care for a quick forced
backdrop I would probably set the default at 10 minutes. What do you think?
Is ten minutes a good default setting! I will see what I can whip up!
P.S. I would still like to optimize the size of the code before uploading
the latest version of RSLClock, so you might not see the new version for a few
more weeks!
BTW, how do you find your CP6 as far as letter quality fonts, speed and
color saturation goes?
-RSL-
As long as the timeout length can be specified, I dont't care about the default
as I load the clock in my startup-sequence. I would prefer five minutes.
The NEC CP6 has a pretty (N)LQ font and is fast. If you use the recommended
sequence of printing colors to make the color ribbon last longer (yellow,
magenta, cyan, black) the colors become darker than on the screen. I usually
use 24 pin/90 dots per inch (nice colors, less saturation) or 24 pin/180 DPI
(darker colors, much saturation). Compared to the 8 pin dot mode also available
on the printer, the 24 pin mode is vastly superior, especially when scaling
down an entire screen to the size of a stamp as my homemade driver can do.
I have a little problem with varying intensity of color, at first believed to
be caused by less impact on the paper by some of the pins, but it may also be
caused by a not so new ribbon. I am investigating that a little more now. The
effect causes horizontal stripes so a colored area will become a bit stripy.
-Joergen
Thanks for the description of the CP6. I have running a version of
RSLCLock\.~~?~?~?~with a timed backdrop screen. The technique to check on whet
whether or not the input device has been used (i.e. the keyboard) is the one
Perry K. demonstrated in an article in Amazing Computing! Either my
implementation is incorrect or its accuracy is questionable. Presently set to
trigger in 10 minutes, it has triggered in any time nc|~?~?~?~ from 10 to 25
minutes! Oh well, back to the drawing board!
-RSL-
Great, Roy. By the way, I just noticed on my system with an external drive DF1
and 1.2, that the clock displays No info for the monitored DF0, when there is
no disk in DF1. Strange, don't you think so ?
-Joergen
Not really that strange. As far as I know the IDCMP Flags can only tell if any
disk has been removed, not any disk specifically. If I didn't disable the info
function and the disk drive in question was empty during "polling" Intuition
would stop your active window and put up a requestor for you to insert a disk
into that disk drive!
Sst Strange but hopefully not too inconvenient!
-RSLP.S. If you've got a better idea I'd
be interested!
Roy, no that isn't too inconvenient, as I always keep a disk in the external
drive to avoid the clicking noise and as I mostly am using both drives.
-Joergen
That's the way that I figured it! It's always a matter of compromising! Now
all I have to do is figure out why what Perry K. did in ScreenSaver doesn't
seem to work "reproducibly" by me. Albeit when I ran SSV to black out in 3
minutes it took more like five or six, but… Oh well… back to the compiler!
-RSL-