home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Club Amiga de Montreal - CAM
/
CAM_CD_1.iso
/
files
/
428.lha
/
PlayMon
/
PlayMon.doc
< prev
next >
Wrap
Text File
|
1990-09-04
|
2KB
|
32 lines
PlayMon V1.0
¯¯¯¯¯¯¯¯¯¯¯¯
SoundMon Player by Xag of The Culprits
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
(Quicky dox by Xag)
This little utility will play SoundMon modules in the background. It takes
the form of a CLI command (sorry to all you lame Quirkbench users). If you
want to start it as a seperate process, use the Run/Runback command. You'll
be alerted if an error crops up and, as with every proggy I write, your
system won't screw up if PlayMon can't allocate enough memory or whatever
(I've seen programs that don't bother checking such things). Once the
proggy has loaded the module, a minute window will open up in the very top
left hand corner of the screen (so you won't get any problems if you use
weird screen sizes). The window can be moved, depth-arranged and closed.
The reason for this window is as follows: most module players exit when you
press the mouse button, wherever the pointer happens to be. They do this
because they test the I/O hardware for a button-pressed condition, which
means that, wherever you click the mouse, the program will always quit.
Another disadvantage of this method is that people usually use a busy loop
to check the register, which REALLY ties up the processor (try running a
module player and press return several times quickly in the CLI window - see
what I mean?). So to exit the proggy, you have to close the window, which
means you can listen and also work with the mouse (using DPaint, CygnusEd or
whatever) and, because I use WaitPort to wait for a CLOSEWINDOW message, the
main program takes up virtually zilch processor time.
Don't bother reporting any bugs etc. cos I only wrote this program for my
convenience - Zigor insisted on spreading it (that's why these docs are so
shit).