feature request: suppress "doesn't understand" in [error] text

Jul 4, 2008 at 6:36pm

feature request: suppress "doesn't understand" in [error] text

Could an argument be added to [error] that suppresses the “doesn’t understand” text and outputs whatever is sent to the object (like print)?

I want to make my own error messages, and have the ability to click on them in the Max window to jump to the object. [error] is almost exactly what I need, but my messages don’t make sense with the “doesn’t understand” text.

#38742
Jul 4, 2008 at 6:50pm

On 4 juil. 08, at 20:36, Adam Murray wrote:

> Could an argument be added to [error] that suppresses the “doesn’t
> understand” text and outputs whatever is sent to the object (like
> print)?
>
> I want to make my own error messages, and have the ability to click
> on them in the Max window to jump to the object. [error] is almost
> exactly what I need, but my messages don’t make sense with the
> “doesn’t understand” text.

Here’s a few workarounds.

ej

– Pasted Max Patch, click to expand. –
#135330
Jul 4, 2008 at 6:57pm

Quote: Emmanuel Jourdan wrote on Fri, 04 July 2008 11:50
—————————————————-
>
> Here’s a few workarounds.
>

Thanks, but I’m asking for something else. Sorry, should have provided a patch in the first place. I want the Max window to say:

my custom error message

instead of

doesn’t understand “my custom error message”

I think your patch shows that [error] is intended for a different purposes then what I want. But this could be really useful! Alternately, maybe [print] could use an attribute that will color it’s message red in the Max window so it looks like an error.

– Pasted Max Patch, click to expand. –
#135331
Jul 4, 2008 at 7:12pm

On 4 juil. 08, at 20:57, Adam Murray wrote:

> Thanks, but I’m asking for something else. Sorry, should have
> provided a patch in the first place. I want the Max window to say:
>
> my custom error message
>
> instead of
>
> doesn’t understand “my custom error message”
>
> I think your patch shows that [error] is intended for a different
> purposes then what I want. But this could be really useful!
> Alternately, maybe [print] could use an attribute that will color
> it’s message red in the Max window so it looks like an error.

indeed ;-) The error message just grab the errors from the Max window,
and not to print errors to the max window. The only way to print
things in red, would be to use js I think:

function anything()
{
error(arrayfromargs(messagename, arguments));
}

HTH,
ej

#135332
Jul 4, 2008 at 8:17pm

Quote: Emmanuel Jourdan wrote on Fri, 04 July 2008 12:12
—————————————————-
> The only way to print
> things in red, would be to use js I think:
>
> function anything()
> {
> error(arrayfromargs(messagename, arguments));
> }
>

That does exactly what I want. Thanks.

I started down this path because I was calling error() from an mxj object and you can’t click on that error message to jump to the object in the patch. Hopefully mxj will be updated so it’s error() method also works this way.

#135333

You must be logged in to reply to this topic.