> > - soundfiler - send a message when a file or an array isn't found. This > > would be useful for the patch to process this information (instead of > just > > showing it in the console) > > E.g. "error file xx not found" and "error array xx not found". This > allows > > to sort out the components using route, unpack, etc. and can be updated > to > > further error types. > > For now the soundfiler reacts with 0 in all outputs. > > isn't this what you want? a message telling you that the read did not > succeed? > i mean, you can use the 0-on-all-outputs messages to determine on a > patch-level that the file couldn't be read. >
The current output is good to know that something went wrong, but not what. Afaik it can be a non-existent file or array - most likely the first. (I don't know if there are other errors with more advanced options). > > > > > - in pd extended, when typing in the name of a new object, the key > > combination ctrl+return would "close" the object. This is now done by > > ctrl+e, which serves for both closing the objects and go in/out of edit > > mode. Currently, presing ctrl+e while editing an object closes the > object, > > but not the edit mode. Is it better to separate these two functions? > > > > well, originally the instantiation of an object via Ctrl+E was just a > side-effect of leaving edit-mode. > Exactly, but a quite useful one. > i haven't noticed myself (but can confirm) the behaviour that Ctrl+E > does not leave edit-mode when currently typing. Yes. Also about that, Ctrl+e while typing gets out of the object. In Pd-Ext, Ctrl+return closed the object, but didn't escaped it. Which made keyboard patching a bit more confortable, as one just types Ctrl+1 and continues patching. Although adding a new object while editing one also closes the previous object and moves on, so for some situations continuity is asured.
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
