On Mon, 2021-06-14 at 10:37 +0200, Peter P. wrote: > * Roman Haefeli <[email protected]> [2021-06-14 10:24]: > [...] > > 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? > Yes, that's a good idea, but what if there are two identical objects > on > the same canvas? > > > 'text /tmp/foo.txt: can't open' > > 'text /tmp/foo.txt: read failed' > I think this could be solved with an extra outlet to [textfile], > [soundfiler], [readsf~] and similar objects without going through the > hassle of inventing a completely parsable error-message object.
Totally. I even would much prefer extra info directly from the object itself. However, I assumed such a change to so many objects is not realistically going to happen. A console parser would work even for externals that do not implement messages through outlets. 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
