| Every thing you say is right, but when I try to drag a csd file onto
WinSound or Console csound it tries to parse the csd as an orc file. What
happens is that Windows converts the filename to ALLCAPS. WinSound and
Console Csound will parse test.csd just fine, but not TEST.CSD. This is a
funny problem, but is definitely a problem in the Csound code, not the
windows code. Without looking at the code, my guess is that csound reads
the last 4 chars of the orchestra file name to see if the file is a csd
file. These four characters should simply be converted to a uniform case
before the logical test.
BTW, DirectCsound doesn't have this problem.
The associations are no problem. I have csd files associated with my text
editor, with three non-default associations to DirectCsound, Console Csound,
and WinSound. Thus, I can right-click and render with the Csound of my
choice. These secondary-associations can be created by editing the
information under the File Types tab of Explorer's "View | Folder Options"
dialog box. You could also place shortcuts to Different Csounds in your
SendTo directory, if the drag-and-drop mechanism worked. (This is a
subdirectory of the Windows directory.) Then you would right click on CSD
file, choose SendTo and choose a Csound. However, If you aren't into
right-clicking, then there is no way to solve the association problem.
-----Original Message-----
From: owner-csound-outgoing@maths.ex.ac.uk
[mailto:owner-csound-outgoing@maths.ex.ac.uk] On Behalf Of Richard Dobson
Sent: Monday, April 12, 1999 5:15 AM
To: csound@maths.ex.ac.uk
Subject: Re: csd files
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
CDP homepage: http://www.bath.ac.uk/~masjpf/CDP/CDP.htm
|