home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Club Amiga de Montreal - CAM
/
CAM_CD_1.iso
/
files
/
138.lha
/
Colors
/
README
< prev
next >
Wrap
Text File
|
1986-11-20
|
4KB
|
126 lines
COLORS
Written by Tom Krehbiel, June 1988
This program in its executable form, along with the assembly source
listing, is in the public domain. They may be freely distributed to any
BBS or person, provide that you (1) be sure you distribute ALL of the
files listed below, and (2) do not charge any fee for distribution (who
would buy this anyway?). Feel free to make any modifications to the source
code you wish, but if you redistribute it, please leave my name in it
someplace. If you have any questions or comments, I can be reached at:
Tom Krehbiel
10747 Surry Road
Chester, VA 23831
or through David Krehbiel (yes, we're related) on Compuserve (70701,1515).
IN THE ARC FILE
The following files should be in the ARC file:
Colors - the program
WB_Colors.info - sample Workbench color icon
CLI_Colors.info - another sample color icon
MyColors - a sample CLI color file
EXECUTE.ME - to rename the files properly
README - this document
I am distributing this mainly for Assembly programmers who are looking
for example code. It is not intended to DO a great deal, although I
find that it works quite well in conjunction with my PopFuncs program (ie,
just program a function key with "`C:Colors -S:My_Colors'" and you can have
a color changer at the touch of a button). Oh well, on to the documentation:
HOW TO RUN IT
Colors can be run three different ways. There are (in the order I
programmed them):
METHOD 1:
1> Colors 000 eef 345 899 (RETURN)
This method works only from CLI (obviously). In this method, you type
the name of the program and then follow it with four sets of rgb color
values. Each rgb set has the form:
<red component><green component><blue component>
where each component is a hex number from 0 to f, representing the
amount of that color. Examples:
f00 would be bright red,
0f0 would be bright green,
00f would be bright blue.
Note that a-f's must be lower case.
METHOD 2:
1> Colors -MyColors
This method also works only from CLI. This way you can put the four
rgb triplets in a disk file, so that you don't have to type them in each
time.
You do this by making a standard text file with the four rgb triplets
(that you would have typed in on the command line in Method 1) at the
very start of the file (NOTE: they must start at the first character of
the file). Then type 'Colors', a space, then a dash, and then the name
of the file containing the rbg triplets. The dash is very important!
As you might have guessed, I did this because I got sick of typing in
long command lines.
METHOD 3:
From the Workbench, double click on a Color Definition icon.
This is the Workbench method. To use this method, you should put the
Colors program in your C: directory (that's why I did this in assembly, so
it wouldn't be very big). Then make a PROJECT icon (see examples in the
ARC file) with the following information:
DEFAULT TOOL - This should have the path name of the Colors program.
If you have it in your C: directory, type this in:
C:Colors
and that should work.
TOOL TYPES - This is where you put the four rgb triplets. Type in
"COLORS=" and then the four rgb triplets just like
you would use in Method 1 or 2. Example:
COLORS=008 fff 000 f50
Note: "COLORS" must be upper case (WB peculiarity).
You can add the above information simply by using the Workbench INFO
option from the Project menu.
AFTERWORD
Well, I guess that's about it. I tried to comment the source code
as much as I could, but if you have trouble reading it or have questions
about why I did something a particular way, let me know. This is actually
*my* first 68K assembly project, so there are probably a few inefficiencies
in it in places.
Have fun with it!
-Tom-