Anthony Palomba

I have discovered a strange difference between the PC and

MAC versions of MAX. I don't know if this is a known MAC

issue but the problem has to do with pattr binding to objects. 

If you take the following and save it as a patcher then load 

it off disk, MAC users should get an error:

* error: pattr: desired name conflicts with class attribute bindto

I have discovered a strange difference between the PC and
MAC versions of MAX. I don't know if this is a known MAC
issue but the problem has to do with pattr binding to objects. 
If you take the following and save it as a patcher then load 
it off disk, MAC users should get an error:

* error: pattr: desired name conflicts with class attribute bindto
* error: 


mac-vs-pc-pattr-behavior-strangeness

Subject: [maxmsp] MAC vs PC pattr behavior strangeness...

> I have discovered a strange difference between the PC and

> MAC versions of MAX. I don't know if this is a known MAC

> issue but the problem has to do with pattr binding to objects. 

> If you take the following and save it as a patcher then load 

> it off disk, MAC users should get an error:

> * error: pattr: desired name conflicts with class attribute bindto

> This does not happen on the PC. I was wondering if anyone was familiar 

> with this problem and what might be the reason for it.

> #P number 276 76 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;

> #P number 234 76 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;

> #P number 192 76 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;

> #P number 150 76 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;

> #P number 107 219 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;

> #P newex 107 242 174 9109513 pattr bindto parent::parent::parent::box4;

> #P number 105 171 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;

> #P newex 105 194 174 9109513 pattr bindto parent::parent::parent::box3;

> #P number 103 123 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;

> #P newex 103 146 174 9109513 pattr bindto parent::parent::parent::box2;

> #P number 101 75 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;

> #P newex 101 98 174 9109513 pattr bindto parent::parent::parent::box1;

----- Original Message ----- 
From: 
To: 
Sent: Monday, August 14, 2006 10:43 AM
Subject: [maxmsp] MAC vs PC pattr behavior strangeness...

> I have discovered a strange difference between the PC and
> MAC versions of MAX. I don't know if this is a known MAC
> issue but the problem has to do with pattr binding to objects. 
> If you take the following and save it as a patcher then load 
> it off disk, MAC users should get an error:
>
> * error: pattr: desired name conflicts with class attribute bindto
> * error: #X: no such object
>
> This does not happen on the PC. I was wondering if anyone was familiar 
> with this problem and what might be the reason for it.
>
>
> Thanks,
> Anthony
>
>
>
> #P window setfont "Sans Serif" 9.;
> #P number 276 76 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P objectname box4;
> #P number 234 76 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P objectname box3;
> #P number 192 76 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P objectname box2;
> #P number 150 76 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P objectname box1;
> #P window linecount 1;
> #N vpatcher 281 309 881 709;
> #P window setfont "Sans Serif" 9.;
> #N vpatcher 149 554 749 954;
> #P window setfont "Sans Serif" 9.;
> #N vpatcher 310 416 910 816;
> #P window setfont "Sans Serif" 9.;
> #P number 107 219 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 107 242 174 9109513 pattr bindto parent::parent::parent::box4;
> #X prestore 1 0 17;
> #P objectname bindto[3];
> #P number 105 171 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 105 194 174 9109513 pattr bindto parent::parent::parent::box3;
> #X prestore 1 0 7;
> #P objectname bindto[2];
> #P number 103 123 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 103 146 174 9109513 pattr bindto parent::parent::parent::box2;
> #X prestore 1 0 27;
> #P objectname bindto[1];
> #P number 101 75 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 101 98 174 9109513 pattr bindto parent::parent::parent::box1;
> #X prestore 1 0 5;
> #P objectname bindto;
> #P connect 1 0 0 0;
> #P connect 3 0 2 0;
> #P connect 5 0 4 0;
> #P connect 7 0 6 0;
> #P pop;
> #P newobj 191 111 41 9109513 p level3;
> #P objectname level3;
> #P pop;
> #P newobj 155 102 41 9109513 p level2;
> #P objectname level2;
> #P pop;
> #P newobj 212 129 41 9109513 p level1;
> #P objectname level1;
> #P comment 258 130 119 9109513
> #P window clipboard copycount 6;
>


Can anyone please tell me why pattr seems 

> This does not happen on the PC. I was wondering if anyone was 

> #P newex 107 242 174 9109513 pattr bindto 

> parent::parent::parent::box4;#X prestore 1 0 17;

> #P newex 105 194 174 9109513 pattr bindto 

> parent::parent::parent::box3;#X prestore 1 0 7;

> #P newex 103 146 174 9109513 pattr bindto 

> parent::parent::parent::box2;#X prestore 1 0 27;

Can anyone please tell me why pattr seems 
to behave differently on MAC and PC?

----- Original Message -----
From: apalomba@austin.rr.com
Date: Monday, August 14, 2006 10:54 am
Subject: [maxmsp] MAC vs PC pattr behavior strangeness...

> I have discovered a strange difference between the PC and
> MAC versions of MAX. I don't know if this is a known MAC
> issue but the problem has to do with pattr binding to objects. 
> If you take the following and save it as a patcher then load 
> it off disk, MAC users should get an error:
>
> * error: pattr: desired name conflicts with class attribute bindto
> * error: #X: no such object
>
> This does not happen on the PC. I was wondering if anyone was 
> familiar 
> with this problem and what might be the reason for it.
>
>
> Thanks,
> Anthony
>
>
>
> #P window setfont "Sans Serif" 9.;
> #P number 276 76 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P objectname box4;
> #P number 234 76 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P objectname box3;
> #P number 192 76 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P objectname box2;
> #P number 150 76 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P objectname box1;
> #P window linecount 1;
> #N vpatcher 281 309 881 709;
> #P window setfont "Sans Serif" 9.;
> #N vpatcher 149 554 749 954;
> #P window setfont "Sans Serif" 9.;
> #N vpatcher 310 416 910 816;
> #P window setfont "Sans Serif" 9.;
> #P number 107 219 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 107 242 174 9109513 pattr bindto 
> parent::parent::parent::box4;#X prestore 1 0 17;
> #P objectname bindto[3];
> #P number 105 171 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 105 194 174 9109513 pattr bindto 
> parent::parent::parent::box3;#X prestore 1 0 7;
> #P objectname bindto[2];
> #P number 103 123 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 103 146 174 9109513 pattr bindto 
> parent::parent::parent::box2;#X prestore 1 0 27;
> #P objectname bindto[1];
> #P number 101 75 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 101 98 174 9109513 pattr bindto parent::parent::parent::box1;
> #X prestore 1 0 5;
> #P objectname bindto;
> #P connect 1 0 0 0;
> #P connect 3 0 2 0;
> #P connect 5 0 4 0;
> #P connect 7 0 6 0;
> #P pop;
> #P newobj 191 111 41 9109513 p level3;
> #P objectname level3;
> #P pop;
> #P newobj 155 102 41 9109513 p level2;
> #P objectname level2;
> #P pop;
> #P newobj 212 129 41 9109513 p level1;
> #P objectname level1;
> #P comment 258 130 119 9109513
> #P window clipboard copycount 6;
>
>


Probably because you are using 2 slightly different versions of the 

objects on the 2 machines. The object on the Mac is complaining that 

it is being named the same name of one of its attributes (in this 

case "bindto"). Don't do that. The most recent PC version should do 

the same, although I don't remember if this change was made 

Since you haven't mentioned what versions Max you are using, it's 

hard to say, but I hope that this will keep you from posting this 

Am 18.08.2006 um 23:05 schrieb apalomba@austin.rr.com:

> Can anyone please tell me why pattr seems

Probably because you are using 2 slightly different versions of the  
objects on the 2 machines. The object on the Mac is complaining that  
it is being named the same name of one of its attributes (in this  
case "bindto"). Don't do that. The most recent PC version should do  
the same, although I don't remember if this change was made  
post-4.5.7 or not.

Since you haven't mentioned what versions Max you are using, it's  
hard to say, but I hope that this will keep you from posting this  
question a 4th time.

> Can anyone please tell me why pattr seems
> to behave differently on MAC and PC?


I see, I am using version 4.5.5 on the PC. I guess it 

So does that mean that in the new PC version (4.5.7) I will no 

longer be able to say "pattr bindto parent::parent::parent::box1"

Subject: Re: [maxmsp] MAC vs PC pattr behavior strangeness...

> Probably because you are using 2 slightly different versions of 

> objects on the 2 machines. The object on the Mac is complaining 

> it is being named the same name of one of its attributes (in this 

> case "bindto"). Don't do that. The most recent PC version should 

> the same, although I don't remember if this change was made 

> Since you haven't mentioned what versions Max you are using, it's 

> hard to say, but I hope that this will keep you from posting this 

> Am 18.08.2006 um 23:05 schrieb apalomba@austin.rr.com:

> > Can anyone please tell me why pattr seems

I see, I am using version 4.5.5 on the PC. I guess it 
is time for me to update.

So does that mean that in the new PC version (4.5.7) I will no 
longer be able to say "pattr bindto parent::parent::parent::box1"
How will I bind to things then?

----- Original Message -----
From: Jeremy Bernstein 
Date: Friday, August 18, 2006 4:16 pm
Subject: Re: [maxmsp] MAC vs PC pattr behavior strangeness...

> Probably because you are using 2 slightly different versions of 
> the  
> objects on the 2 machines. The object on the Mac is complaining 
> that  
> it is being named the same name of one of its attributes (in this  
> case "bindto"). Don't do that. The most recent PC version should 
> do  
> the same, although I don't remember if this change was made  
> post-4.5.7 or not.
>
> Since you haven't mentioned what versions Max you are using, it's  
> hard to say, but I hope that this will keep you from posting this  
> question a 4th time.
>
> jb
>
> Am 18.08.2006 um 23:05 schrieb apalomba@austin.rr.com:
>
> > Can anyone please tell me why pattr seems
> > to behave differently on MAC and PC?
>
>


The first argument to pattr is the name of the object. The 2nd 

argument can be the name of an object to bind to, but I think it's 

better to use the bindto attribute explicitly.

What you want to write is "pattr somename @bindto 

parent::parent::parent::box1". This is all documented in the Max 

Am 19.08.2006 um 00:23 schrieb apalomba@austin.rr.com:

> I see, I am using version 4.5.5 on the PC. I guess it

> So does that mean that in the new PC version (4.5.7) I will no

> longer be able to say "pattr bindto parent::parent::parent::box1"

> Subject: Re: [maxmsp] MAC vs PC pattr behavior strangeness...

>> Probably because you are using 2 slightly different versions of

>> objects on the 2 machines. The object on the Mac is complaining

>> it is being named the same name of one of its attributes (in this

>> case "bindto"). Don't do that. The most recent PC version should

>> the same, although I don't remember if this change was made

>> Since you haven't mentioned what versions Max you are using, it's

>> hard to say, but I hope that this will keep you from posting this

>> Am 18.08.2006 um 23:05 schrieb apalomba@austin.rr.com:

>>> Can anyone please tell me why pattr seems

The first argument to pattr is the name of the object. The 2nd  
argument can be the name of an object to bind to, but I think it's  
better to use the bindto attribute explicitly.

What you want to write is "pattr somename @bindto  
parent::parent::parent::box1". This is all documented in the Max  
Reference Manual, too.

> I see, I am using version 4.5.5 on the PC. I guess it
> is time for me to update.
>
> So does that mean that in the new PC version (4.5.7) I will no
> longer be able to say "pattr bindto parent::parent::parent::box1"
> How will I bind to things then?
>
>
> Anthony
>
>
> ----- Original Message -----
> From: Jeremy Bernstein 
> Date: Friday, August 18, 2006 4:16 pm
> Subject: Re: [maxmsp] MAC vs PC pattr behavior strangeness...
>
>> Probably because you are using 2 slightly different versions of
>> the
>> objects on the 2 machines. The object on the Mac is complaining
>> that
>> it is being named the same name of one of its attributes (in this
>> case "bindto"). Don't do that. The most recent PC version should
>> do
>> the same, although I don't remember if this change was made
>> post-4.5.7 or not.
>>
>> Since you haven't mentioned what versions Max you are using, it's
>> hard to say, but I hope that this will keep you from posting this
>> question a 4th time.
>>
>> jb
>>
>> Am 18.08.2006 um 23:05 schrieb apalomba@austin.rr.com:
>>
>>> Can anyone please tell me why pattr seems
>>> to behave differently on MAC and PC?
>>
>>


I see, I will it do that way from now on.

> The first argument to pattr is the name of the object. The 2nd 

> argument can be the name of an object to bind to, but I think it's 

> better to use the bindto attribute explicitly.

> What you want to write is "pattr somename @bindto 

> parent::parent::parent::box1". This is all documented in the Max 

> Am 19.08.2006 um 00:23 schrieb apalomba@austin.rr.com:

> > I see, I am using version 4.5.5 on the PC. I guess it

> > So does that mean that in the new PC version (4.5.7) I will no

> > longer be able to say "pattr bindto parent::parent::parent::box1"

> > Date: Friday, August 18, 2006 4:16 pm

> > Subject: Re: [maxmsp] MAC vs PC pattr behavior strangeness...

> >> Probably because you are using 2 slightly different versions of

> >> objects on the 2 machines. The object on the Mac is complaining

> >> it is being named the same name of one of its attributes (in this

> >> case "bindto"). Don't do that. The most recent PC version should

> >> the same, although I don't remember if this change was made

> >> Since you haven't mentioned what versions Max you are using, it's

> >> hard to say, but I hope that this will keep you from posting this

> >> Am 18.08.2006 um 23:05 schrieb apalomba@austin.rr.com:

> >>> Can anyone please tell me why pattr seems

> >>> to behave differently on MAC and PC?

----- Original Message ----- 
From: "Jeremy Bernstein" 
To: 
Sent: Friday, August 18, 2006 8:12 PM
Subject: Re: [maxmsp] MAC vs PC pattr behavior strangeness...

> The first argument to pattr is the name of the object. The 2nd  
> argument can be the name of an object to bind to, but I think it's  
> better to use the bindto attribute explicitly.
>
> What you want to write is "pattr somename @bindto  
> parent::parent::parent::box1". This is all documented in the Max  
> Reference Manual, too.
>
> jb
>
> Am 19.08.2006 um 00:23 schrieb apalomba@austin.rr.com:
>
> > I see, I am using version 4.5.5 on the PC. I guess it
> > is time for me to update.
> >
> > So does that mean that in the new PC version (4.5.7) I will no
> > longer be able to say "pattr bindto parent::parent::parent::box1"
> > How will I bind to things then?
> >
> >
> > Anthony
> >
> >
> > ----- Original Message -----
> > From: Jeremy Bernstein 
> > Date: Friday, August 18, 2006 4:16 pm
> > Subject: Re: [maxmsp] MAC vs PC pattr behavior strangeness...
> >
> >> Probably because you are using 2 slightly different versions of
> >> the
> >> objects on the 2 machines. The object on the Mac is complaining
> >> that
> >> it is being named the same name of one of its attributes (in this
> >> case "bindto"). Don't do that. The most recent PC version should
> >> do
> >> the same, although I don't remember if this change was made
> >> post-4.5.7 or not.
> >>
> >> Since you haven't mentioned what versions Max you are using, it's
> >> hard to say, but I hope that this will keep you from posting this
> >> question a 4th time.
> >>
> >> jb
> >>
> >> Am 18.08.2006 um 23:05 schrieb apalomba@austin.rr.com:
> >>
> >>> Can anyone please tell me why pattr seems
> >>> to behave differently on MAC and PC?
> >>
> >>
>
