KJolly

Is there a simple way to know which pattr object has failed to bind to it's target? I've got tons of them and can figure out which one is failing.

pattr-question-how-do-you-find-which-one-has-failed-to-bind

I would love to know this as well. It is so annoying that 

pattr does not print the name of the control that it can not 

bind to. The easiest way I can think of is open the patcher as

a text file and find matching pairs of "bindto" and "newobj" 

Date: Wednesday, October 11, 2006 11:42 am

Subject: [maxmsp] Pattr Question - how do you find which one has failed 

> Is there a simple way to know which pattr object has failed to 

> bind to it's target? I've got tons of them and can figure out 

I would love to know this as well. It is so annoying that 
pattr does not print the name of the control that it can not 
bind to. The easiest way I can think of is open the patcher as
a text file and find matching pairs of "bindto" and "newobj" 
statements.

----- Original Message -----
From: KJolly 
Date: Wednesday, October 11, 2006 11:42 am
Subject: [maxmsp] Pattr Question - how do you find which one has failed 
to	bind?

>
> Is there a simple way to know which pattr object has failed to 
> bind to it's target? I've got tons of them and can figure out 
> which one is failing. 
>
> thanks for any help.
>
> kj
>
>


Recent versions of pattr print out both the name of the pattr and the 

name of the target which couldn't be bound to. What other information 

Am 11.10.2006 um 20:44 schrieb apalomba@austin.rr.com:

> I would love to know this as well. It is so annoying that

> pattr does not print the name of the control that it can not

> bind to. The easiest way I can think of is open the patcher as

> a text file and find matching pairs of "bindto" and "newobj"

> Date: Wednesday, October 11, 2006 11:42 am

> Subject: [maxmsp] Pattr Question - how do you find which one has 

>> Is there a simple way to know which pattr object has failed to

>> bind to it's target? I've got tons of them and can figure out

Recent versions of pattr print out both the name of the pattr and the  
name of the target which couldn't be bound to. What other information  
do you need?

> I would love to know this as well. It is so annoying that
> pattr does not print the name of the control that it can not
> bind to. The easiest way I can think of is open the patcher as
> a text file and find matching pairs of "bindto" and "newobj"
> statements.
>
>
>
> Anthony
>
>
>
>
> ----- Original Message -----
> From: KJolly 
> Date: Wednesday, October 11, 2006 11:42 am
> Subject: [maxmsp] Pattr Question - how do you find which one has  
> failed
> to	bind?
>
>>
>> Is there a simple way to know which pattr object has failed to
>> bind to it's target? I've got tons of them and can figure out
>> which one is failing.
>>
>> thanks for any help.
>>
>> kj
>>
>>


Oh boy how I'd -love- to be able to click an error in the max window and jump to the object that printed it..

> Is there a simple way to know which pattr object has failed to bind

> to it's target? I've got tons of them and can figure out which one is

This issue isn't pattr specific. I'd really like to see some debuggiing 

enhancements for Max 5. For example a way to localise an object which 

At the moment the only way to find out is to "unpatch" the patch bit by 

KJolly wrote:
> Is there a simple way to know which pattr object has failed to bind
> to it's target? I've got tons of them and can figure out which one is
> failing.

This issue isn't pattr specific. I'd really like to see some debuggiing 
enhancements for Max 5. For example a way to localise an object which 
spits out an error message...

At the moment the only way to find out is to "unpatch" the patch bit by 
bit, till it stops doing it...

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


> Oh boy how I'd -love- to be able to click an error in the max window

> and jump to the object that printed it..

I second that, might make it to the most demanded feature request for Max 5!

Mattijs Kneppers wrote:
> Oh boy how I'd -love- to be able to click an error in the max window
> and jump to the object that printed it..

> Recent versions of pattr print out both the name of the pattr and the 

> name of the target which couldn't be bound to. What other information 

Of course the object which sent the message. But as there is no aid yet 

to find out where this object is placed, we probably have to wait for 

Jeremy Bernstein wrote:
> Recent versions of pattr print out both the name of the pattr and the  
> name of the target which couldn't be bound to. What other information  
> do you need?

Of course the object which sent the message. But as there is no aid yet 
to find out where this object is placed, we probably have to wait for 
Max 5...

Quote: VG wrote on Mon, 16 October 2006 15:49

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

> and to be able to get the error message from the max window directly

> and the send~ and receive~ to behave like send and receive

> than you can click to see other instances..

Oh yeah and the multi-level find and replace function that also searches locked patchers.

That's why I'd really love C74 to be the first company with an online registered feature requests log. I have tons of these improvements that I would submit if I wouldn't assume that they are already on a list somewhere. I hate annoying hardworking developers with info they already have.

But what if one of my idea's is not on this list and it happens to be a prize-winning upgrade idea that I am willing to submit to cycling for free? Like the idea of an online registered feature requests log ;)

Quote: VG wrote on Mon, 16 October 2006 15:49
----------------------------------------------------
> o yeah!
> and to be able to get the error message from the max window directly
> into max messages to reuse them.
> and the send~ and receive~ to behave like send and receive
> than you can click to see other instances..
> same for the forward object.

Oh yeah! And for the grab object!
Oh yeah and the multi-level find and replace function that also searches locked patchers.
Oh yeah and the multiple undo's.
And..
And..

That's why I'd really love C74 to be the first company with an online registered feature requests log. I have tons of these improvements that I would submit if I wouldn't assume that they are already on a list somewhere. I hate annoying hardworking developers with info they already have. 

Pattr Question - how do you find which one has failed to bind?