WBClock
-------

I wanted a clock that wouldn't be using up valuable window space.

I thought, "Hey, most other systems have iconisable clocks that keep telling
the time as icons on the desk top."

I looked for one.  Not real hard, but I had a look at all the clocks on
aminet etc, but failed to find one.

I spent not very long at all writing wbclock.

I realized _why_ people had not written one for the workbench (should have
been obvious from the start, but well, sometimes I'm a bit slow).  The sad
sad sad updating of icons on the workbench is so farcicle.

Anyway, this is the result.  It is completely in the public domain.  You can
use the code to do whatever you please.  The algorithms for drawing lines,
clearing circles etc are quite poor.  They work ok though.  Things it
probably should do but doesn't include support for locale, putting its hand
up to be in the commodities list, alarms and configurability.  If you want
'em you can add 'em.  None should be too difficult.

The icon is based on MagicWB colours and style.  You are free to replace the
icon with another, and it should work fine provided that the icon has circles
of the same size in the normal and selected images which are centred and
offset 1 pixel down and right respectively.

The program draws the clock hands OVER IT'S OWN ICON.  Hence a simple way to
install it is to drop it in your WBStartup drawer, and then "Leave Out" and
snapshot it onto your desktop somewhere.  If the program stops unexpectedly,
it will of course stop moving  the hands around, but the icon will still be
shown on the workbench ... If you run wbclock again, it will shutdown the
original.

Because it is doing a PutDiskObject every minute it will access whatever
medium _every_ _minute_.  You may find this irritating if you have a noisy
drive.  Perhaps launching it from ram would be ok, but this takes
significantly more fiddling to set up.

Also because of the sad way the icon updating is done, if the icon is on
your desktop, every minute all the icons will be refreshed ... this is
the worst flaw of this clock.  See if it is too annoying ... I suspect many
people will find it so.

This was compiled with SAS 6.50, and ran on my GVP 030 upgraded 2000 under
both 2.1 and 3.0.  It does nothing unpleasant so I can't see why it won't
run under any system with 2.0 or later.

Anyway, have fun,
Evan.

evan@ucc.gu.uwa.edu.au

PS: I do not intend to do any more work on this, so do not bother to contact
me with suggestions.  (or complaints, or flames, or anything else)