Adam Murray

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.

feature-request-suppress-doesnt-understand-in-error-text

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 

> 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 

> 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.

Quote: Emmanuel Jourdan wrote on Fri, 04 July 2008 11:50

----------------------------------------------------

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:

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.

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

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:

> 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:

    error(arrayfromargs(messagename, arguments));

> 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));
}

Quote: Emmanuel Jourdan wrote on Fri, 04 July 2008 12:12

> things in red, would be to use js I think:

>     error(arrayfromargs(messagename, arguments));

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.

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));
> }
>

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.


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