On Mon, 2021-06-14 at 10:02 +0200, Peter P. wrote: > I am wondering how one would > parse these error messages if they came from one single object outlet > to > tell where the error originated from?
I am wondering about that, too. Maybe a [pderror] would be canvas-local and only report errors from objects belonging to the local canvas? And it would prepend the name of the object to the message? For instance: 'netsend netsend: bad host or port? Name or service not known (-2)' or 'netsend connecting stream socket: Interrupted system call (4)' Obviously, those messages are not intended for parsing, but having them available to the patch would still be immensely useful. Another one I so often wished I get proper feedback for: 'text /tmp/foo.txt: can't open' 'text /tmp/foo.txt: read failed' Roman
signature.asc
Description: This is a digitally signed message part
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
