On Thu, 6 Dec 2007, marius schebella wrote:
"find last error", even if this does not work all the time, it really helped me save a lot of time.
Btw, "find last error" in DesireData works pretty much all of the time.
In PureData, "find last error" relies on the good will of external (and internal) developers to use pd_error() instead of error(). In DesireData, pd_error() is obsolete and deprecated.
With a little more work, DesireData's "find last error" will be able to actually select all objects involved in the message chain leading to the error! e.g.:
[loadbang] | [tgl] | [metro 666] | [f] | [symbol]
would select the last three objects, because [metro]'s bang led to 0 which led to "no method for float". the start of the message chain is usually [metro], [delay], [gemhead] and other clock-driven classes (so [tgl] can't be found to be the ancestor of the error).
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada