Hi all,
I'm creating patches that print error messages to the console.
Is it possible to send a special error message that would be trackable by Pd's 'Find>Find last error' command?
Many thanks in advance, John.
Pd doesn't have an internal object that can do that. But the pd_error function is in m_pd.h. That means someone can easily make an external [error] that takes an incoming pd message and outputs it as a pd error. Doing so would print a trackable error to the console that tracks back to the relevant [error] object that generated the error. There is probably already an object that does that in the big pile of Pd-extended externals.
-Jonathan
On Friday, January 8, 2016 5:38 AM, JF via Pd-list <pd-list@lists.iem.at> wrote:
Hi all,
I'm creating patches that print error messages to the console.
Is it possible to send a special error message that would be trackable by Pd's 'Find>Find last error' command?
Many thanks in advance, John.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Well, I guess it's the function _prototype_ that's in m_pd.h, to be precise... -Jonathan
On Friday, January 8, 2016 11:47 AM, Jonathan Wilkes via Pd-list <pd-list@lists.iem.at> wrote:
Pd doesn't have an internal object that can do that. But the pd_error function is in m_pd.h. That means someone can easily make an external [error] that takes an incoming pd message and outputs it as a pd error. Doing so would print a trackable error to the console that tracks back to the relevant [error] object that generated the error. There is probably already an object that does that in the big pile of Pd-extended externals.
-Jonathan
On Friday, January 8, 2016 5:38 AM, JF via Pd-list <pd-list@lists.iem.at> wrote:
Hi all,
I'm creating patches that print error messages to the console.
Is it possible to send a special error message that would be trackable by Pd's 'Find>Find last error' command?
Many thanks in advance, John.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
The log library has just such an [error].
On Fri, Jan 8, 2016 at 11:51 AM, Jonathan Wilkes via Pd-list < pd-list@lists.iem.at> wrote:
Well, I guess it's the function _prototype_ that's in m_pd.h, to be precise...
-Jonathan
On Friday, January 8, 2016 11:47 AM, Jonathan Wilkes via Pd-list < pd-list@lists.iem.at> wrote:
Pd doesn't have an internal object that can do that.
But the pd_error function is in m_pd.h. That means someone can easily make an external [error] that takes an incoming pd message and outputs it as a pd error. Doing so would print a trackable error to the console that tracks back to the relevant [error] object that generated the error.
There is probably already an object that does that in the big pile of Pd-extended externals.
-Jonathan
On Friday, January 8, 2016 5:38 AM, JF via Pd-list pd-list@lists.iem.at wrote:
Hi all,
I'm creating patches that print error messages to the console.
Is it possible to send a special error message that would be trackable by Pd's 'Find>Find last error' command?
Many thanks in advance, John.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On 01/08/2016 05:46 PM, Jonathan Wilkes via Pd-list wrote:
Pd doesn't have an internal object that can do that. But the pd_error function is in m_pd.h. That means someone can easily make an external [error] that takes an incoming pd message and outputs it as a pd error. Doing so would print a trackable error to the console that tracks back to the relevant [error] object that generated the error. There is probably already an object that does that in the big pile of Pd-extended externals.
a couple: the "log" library has an [error] object, which does exactly this.
i find this a bit inconvenient because the "find last error" will get you to the [error] object itself, rather than to the object that actually threw the error (the abstraction wherein the [error] was generated).
therefore, iemguts' [canvaserror] will mark an upstream canvas as the trackable object, so the user is lead to the (imo) "correct" object.
gfmadsr IOhannes