Hi all,
>> - errors: >> in pd many objects print their errors to the console, which makes it >> impossible to take them into account within a patch. i think this is a >> big flaw (if it pd is considered to be a programming language [and that >> is how i use pd]) >> > > objects should give good error messages, and there should be an > infrastructure to handle errors ... > there is already the infrastructure to throw and track exceptions, > however it is not widely used, yet ... > > most of the external objects that i developed lately (mostly for vibrez) use an additional right outlet (normally used as a dump or attribute outlet) for error reports. An [error xxxx( message is generated whenever an exception happens, which can than be digested by the patcher logic. For older pd objects we use we implemented a "console hook" that reads the error messages off the console and redirects them into the patcher. It's a bad hack that probably generates a lot of symbols but works fine so far. >> - reporting: >> many objects are able to print their current state (connection, on/off, >> whatsoever) to the console, but not to an outlet. others don't report >> their state at all, while reporting would be helpful. >> > > this is somehow related to `attributes' ... i was thinking about > flext/jitter-like attributes for nova, haven't been finding a powerful > way to use and define them, yet ... > > You could have a look at the Max/Jitter API.... attributes are defined on a low (class) level which makes it easy for the system to perform various things on them, e.g. subject them to the automation/presetting system etc. gr~~~ _______________________________________________ nova-dev mailing list [email protected] http://klingt.org/cgi-bin/mailman/listinfo/nova-dev http://tim.klingt.org/nova
