ColourKwik v1.01

                       Author : Adam Lock

                 Copyright 1991 Amiga Computing

If you have any queries regarding this program then, the author
can be contacted by electronic mail the following address:

                     cmp9133@uk.ac.uea.sys

                           DESCRIPTION

     ColourKwik is a simple, easy to use program that allows the
user to modify the colours on any intuition based screen, and
store them for later use.
     There are several reasons why a program like this is useful:

a. Many a useful program has been completely ruined by the
authors awful colour scheme that (s)he built into it. Instead of
deleting that wonderful omni-macro text editor which uses magenta
ink on an orange paper, you can now use ColourKwik with your
favorite colour scheme. People who experience colour-blindness
(or good taste) might be grateful for this.

b. Whilst writing other programs I have noticed that the need to
work out colour schemes is always one task. Now, instead of
messing around with DPaint and a dummy snapshot of your screen,
you can now run your program, and fine tune your colours with
ColourKwik.

c. Every now and again, one comes across a program with a very
nice colour scheme and it is nice to be able to see how the
colours relate to each other and use similar ideas in your own
programs/art.


Running ColourKwik

From CLI - Just type in ColourKwik [return], and the program will 
execute. Your command line will be restored since ColourKwik runs
as a background task.

From WB - Just double-click on the associated icon to start
ColourKwik.


Changing Colours

Nothing could be simpler. Just click on the colour you wish to
change. This will then appear in the box on the right hand side
of the ColourKwik window. To alter the colour, use the up and
down gadgets to change the amount of red, green and blue in the
colour.

Jumping from screen to screen

In the ColourKwik window is a gadget called JUMP. If you have
more than one screen open, then by pressing this, the window will
close on the current screen and reopen on the next screen.

Load/Save Operations

If you click on load or save then an ARP file requestor will
appear and allow you to retrieve/store palettes. Obviously if you
do not have the arp.library installed in your libs: directory
then ColourKwik will not be able to use this selector. Instead a
single file in the s: directory  called 'palette', will be used
for all disk operations.

The Depth Gadgets

These are provided so that ColourKwik does not have to stay in
the foreground all the time on screens like workbench. If however
you want to use these gadgets on any other screen you MUST be
sure that all the other windows have depth gadgets as well.
Otherwise it might be impossible to retrieve the ColourKwik
window.

Quitting ColourKwik

Using the standard Close Window gadget, will cause ColourKwik to
exit whatever screen it is on.

Quitting From the Host Program

If the screen that ColourKwik is operating on is closed, then
ColourKwik will be lost in limbo, and the memory that it used
will be lost. You must either JUMP or QUIT before closing the
screen.


                    Limitations of ColourKwik

ColourKwik uses intuition to jump around between programs. This
means that if the program disables intuition, you cannot use
ColourKwik to change its colours.

Some programs do not expect intruders leaping onto their
screens,and consequently do not refresh their windows when
ColourKwik is put on top of them. This means that when ColourKwik
is moved/quit/jumped it will leave a hole in the window
underneath. DPaint is like this.

If a program has a spare copy of its palette and reloads it
frequently then all the changes will be reset. Since most
programs that do this have their own palette customizer this is
not much of a worry.

ColourKwik is not permanent, so that when the host program is
reexecuted, the new colour scheme needs to be reloaded.