Ge Wang wrote:
bugs - to be fixed by 1.2.0.7 or earlier.
I also mentioned: 1) It's not possible to extend a public class with a private one in the same file: class myEvent extends Event{ int value; } public class bla{ myEvent some_event; }
missing features, in addition to the usual ones (strings etc.)
I also proposed: 1) Reuse of old, unused shred ids. Should maybe be turned on/off my commandline switch, since in some cases it might be useful to have chuck work the way it is now. It would also be nice to kick a running ckuck and get the ids ordered from 1 to nb_running_shreds without holes in the numbering.
2. multiple class declarations over time (a better way to deal with classes on-the-fly)
Is this the same as "can't replace class definitions on-the-fly"? Documentaion: 1) It it's possible to write instruments that extends StkInstruments (either in userspace chuck or in C) documentation of how to do this would be nice. 2) More detailed information about what a static declaration means (quickie: the data/functions are shared by all instances) and doesn't mean (it doesn't mean that the data can't be altered). This might be obvious for users familiar with C, but not all people code C. -- peace, love & harmony Atte http://www.atte.dk | quartet: http://www.anagrammer.dk http://www.atte.dk/gps | compositions: http://www.atte.dk/compositions