This should happen anyway - I can file up Winsound just dragging a text
file to it (lots of error msgs or course, but it launches). The real
issue is double-clicking a file - i.e setting up an 'association'; e.g
by d-clicking a csd file, and when Windows puts up the dialog asking
which program to use to open the file, just put in the path to Winsound
(or browse using the 'Other' button).

Programmatically, it can be done by defining a document type (this is an
MFC thing), and then calling EnableShellOpen() and 
RegisterShellFileTypes().

The problem with this is exactly that anyone using both Winsound and
AXCsound will want the association with one or the other. However, just
about any file can be dragged to an icon - all that happens is that
Windows passes it in the command line. So long as Winsound can handle
nothing but a csd file as a commandline arg, all is well!

Richard Dobson

jpff@maths.bath.ac.uk wrote:
> 
> Message written at 11 Apr 1999 19:11:22 +0530
> --- Copy of mail to Christopher.Neese@oberlin.edu ---
> 
> I had not given any tought to dragging a csd file onto the winsound
> icon, but clearly I ought to have done.  I will look into it.
> ==John ffitch

-- 
Test your DAW with my Soundcard Attrition Page!
http://wkweb5.cableinet.co.uk/rwd