[PD] Ability to access error messages from patch
reduzent at gmail.com
Mon Jun 14 10:23:43 CEST 2021
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
> 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?
'netsend netsend: bad host or port? Name or service not known (-2)'
'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'
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: This is a digitally signed message part
More information about the Pd-list