[Bluemusic-users] UDO Manager question
Brought to you by:
kunstmusik
From: Steven Yi <ste...@gm...> - 2005-05-20 01:50:27
|
Hi All, I'm in the middle of finishing off the UDO manager, and currently I have it where it will parse out alot of information. However, I'm not sure if it's the best way, as I'm now taking a look at a working version, and it seems some of the information is easier to understand if it's within the code body. I've attached a screenshot png file to demonstrate in its current form. So, I am thinking that it might be better to just have OpcodeName, InTypes, and OutTypes parsed. The other information could be left within the code body (OutArgs, InArgs, using local ksmps). I think that makes the code easier to read. Originally I had thought by parsing out the information, it would be easier to have it for adding the UDO's to blue's autocompletion (ctrl-space) feature. I think though that I might be able to do without it and just parse it from the text every time. Any thoughts? I'm about to make the change to simplify the code now and only parse name, in-, and out-types, but wouldn't be hard to revert. Thanks! steven |