Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!samsung!uunet!mcsun!hp4nl!maestro!beo
From: beo@maestro.htsa.aha.nl (BeO de PeO)
Newsgroups: comp.sys.amiga.tech
Subject: Re: ^G in WorkBench 1.4
Message-ID: <1160@maestro.htsa.aha.nl>
Date: 13 Nov 89 12:06:53 GMT
References: <3742@altos86.Altos.COM> <1159@maestro.htsa.aha.nl> <3260@jhunix.HCF.JHU.EDU> <4518@sugar.hackercorp.com> <3271@jhunix.HCF.JHU.EDU>
Reply-To: beo@maestro.htsa.aha.nl (BeO de PeO)
Organization: AHA-TMF (Technical Institute), Amsterdam, The Netherlands
Lines: 18

In article <3271@jhunix.HCF.JHU.EDU> barrett@jhunix.UUCP (Dan Barrett) writes:
>>and In several articles several people write a lot:
>	Mainly to make the software a little idiot-proof.  I have seen
>plenty of programs that allow multiple control-G's to get sent quickly.
>If the "beep" sound is long, should it (a) restart as it receives each
>^G, (b) overlap itself, using the other audio channels, (c) ignore ^G's
>that occur while a previous ^G is still playing, (d) play them one right
>after the other, with the end of one sound going into the beginning of the
>next?

Let's make a SOUND: directory, which has a default of S: or DEVS: when
not specified, and some kinda mountlist (like) file (Sountlist ? :^) In 
which you can specify above options. 
It would also be nice, if, optionally of course, a list of soundnames can
be read from which a sound can be played at random.
(*8  Any more suggestions ?  8*)

Greetings: Jan van Veen, beo@maestro.htsa.aha.nl (beo de peo)