[PD] prevent console error messages

Roman Haefeli reduzent at gmail.com
Wed Oct 14 09:34:19 CEST 2015

On Wed, 2015-10-14 at 09:09 +0200, IOhannes m zmoelnig wrote:
> On 2015-10-13 15:43, Jonathan Wilkes via Pd-list wrote:
> > What are some of those legitimate uses?
> > A legitimate use of an object should not be generating 
> > an error in the first place.
> +1
> well, more or less.
> e.g. accessing a non-existing or locked ressource is a legitimate use of
> an object and should nevertheless be reported back.
> ideally, it would be reported back to the patch (so that (the author of)
> the patch can react appropriately, rather than the user , but tradition
> has it that Pd reports such situations by itself.
> this makes it nigh impossible to e.g. check for the existence of a file
> in Pd (vanilla) without generating an error-message as a side-effect.
> this might be annoying but i'm not sure whether i would like this
> behaviour to be "fixed".

Why not?

I desperately needed this functionality and I found a solution that does
_not_ cause an error. However, it requires object classes from three
different libraries (zexy, ggee, moocow):

I don't see why [textfile] shouldn't report that to the patch instead of
the console. 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20151014/8b39d439/attachment.sig>

More information about the Pd-list mailing list