home *** CD-ROM | disk | FTP | other *** search
- _ _
- // - DClock v1.5 - //
- _ // * A Dumb Clock Utility * _ //
- \X/ \X/
- BACKGROUND:
- -----------
- Who cares for clock utilities, really, who does? Well, I do. I
- needed one, but couldn't find anything suitable. The standard
- Workbench clock was a bit too big, Mclk slowed down system
- performance, TUC had far too many features (including occasional
- disk-thrashing), RSLClock was too large, so was MachII and DMouse
- intentionally didn't have any clock display. So, what was I up to do?
- Right, I programmed my very special creation, short, sweet and
- functional.
-
- FEATURES:
- ---------
- Since I have already cooked out my custom version of DMouse I didn't
- need any additional Mouse accelerator, so this one didn't get into it.
- What I needed were Date (including weekday) and Time.
- The most important question was: where to place the display?
- Since I have already tested Mouse pointer clocks and my home brewn
- MouseClock program which features two sprites hovering at the right
- hand side of the Mouse pointer, the answer could only be: put it on
- the Workbench screen.
- Remembering my experiences with ReadySoft's A-Max Apple
- MacIntosh Emulator the time display found its way to the right hand
- side of the Workbench title bar. The time string is updated each
- second.
- DClock needs arp.library v39.1 (DClock-Handler doesn't). And
- as far as I am concerned, a memory usage bar can be quite a useful
- thing. Pressing RIGHT-AMIGA+HELP draws some memory statistics into
- the DClock window (this nasty feature sneaked in in version 1.3, I
- can't be blamed for any consequences).
- Mclk uses about 10% of CPU time and about 16000 bytes of
- memory (that's almost as much as the standard Workbench clock
- consumes), MachII uses 4% of CPU time and 32000 bytes. DClock only
- consumes between 1% and 3% of CPU time and requires only 10000 bytes
- of memory (well, became some more during the last revisions, didn't
- want to change the text, looks so impressive) - note that this also
- includes the keyboard click, the display beep, the memory display and
- the time string to be updated each second.
-
- INSTALLATION:
- -------------
- Place DClock-Handler in L:, DClock in C: or SYS:, arp.library in
- LIBS:, type DClock to install, DClock quit to remove. Easy, isn't it?
- I do not advise you to start DClock from Workbench, but if I can't
- keep you from doing so, it's you who's responsible for all negative
- side effects (if there are any... are there?).
-
- EXTRAS:
- -------
- DClock still isn't a pure Clock Utility. I was used to install a
- program called DisplayBeep in my Startup-Sequence script. This
- program spawns a process which replaces the DisplayBeep() function
- with a substitute which does not only flash the display but also beeps
- audibly. To save some memory the code of DisplayBeep.c has been
- incorporated into DClock-Handler.c. I also added the Click.c code I
- had written back in October. Somebody asked me to add an alarm-clock
- function. Well, took me two hours to program it.
-
- CREDITS:
- --------
- Credits go to ARP Programmers for the most recent version of ARP, to
- Matt Dillon for DMouse, to Mike Oldfield & Peter Norman for the
- keyboard click, to John Hodgson for the beep and to Justin V.
- McCormick for the string formatting code.
- A special mention must also go to Bill Hawes, author of ARexx
- and to the authors of CygnusEd Professional (Bruce Dawson & Steve
- LaRocque?) whose programs both controlled the compiler runs.
-
- COPY FEE, AUTHORS REQUEST, ETC.:
- --------------------------------
- If you like DClock program and wish to contribute any money I urge you
- to send at least 5$ to...
-
- Amnesty International
- P.O. Box 37137
- Washington D.C. 20013
-
- I suppose Amnesty International can make better use of the money than
- I can. Even the smallest contribution makes sense.
-
- I don't care what happens to DClock and DClock-Handler, copy them,
- sell them, delete them, they are meant to be PUBLIC-DOMAIN. But don't
- 'fleece' other users for them. Permission to redistribute the
- documentation, the source code and executable files granted as long as
- the body of this document is left intact.
-
- -
-
- I have tried to make DClock as flexible as possible. The rendezvous
- data is easily to be extended. I encourage you to add whatever
- feature you want. I only ask you to send me a copy of your custom
- version of DClock. The future of this tool depends on you, spread the
- word and also the disk! My address is:
-
- Olaf Barthel
- Brabeckstrasse 35
- D-3000 Hannover 71
-
- Federal Republic of Germany
-
-
- REVISION HISTORY (most recent change first):
- --------------------------------------------
- V1.5 Added a most unnerving alarm clock function: the display
- vibrates, a bell is ringing ... what can it be? Probably
- DClock trying to wake you up.
-
- V1.4 Fixed bug in time signal routine (didn't update if seconds
- were reset to a point of time already passed), added status
- line information, corrected exit() calls in DClock.
-
- V1.3 Played around with a taller custom font (saw Kickstart 1.4
- alpha 15 and noticed that the Workbench status line became
- longer overrriding the DClock display). The font didn't get
- into it. Added a numeric memory display.
-
- V1.2 Thought of incorporating the code of Click and DisplayBeep
- into DClock and added them. Also stumbled upon my old
- MemGauge program and added a memory gauge display.
-
- V1.1 Added ARP interface, replaced standard DOS calls with ARP
- calls, removed the clock display from the barlayer (always
- crashed after a call to CloseWorkBench()), added weekday
- conversion and command line options.
-
- V1.0 Simple ('dumb') backdrop clock with date and time display
- to be rendered directly into the Workbench bar layer.
-
- *
-
- Do only its possibilities make it an Amiga?
-
- WHERE IS THE MAGIC ???
-