Forums > MaxMSP

bug? pattrhub responds in wrong order

September 24, 2006 | 7:36 pm

Hi, I am troubled by a strange problem. The patch below illustrates it.

I send pattrhub two messages, first ‘getVar’ (referring to a pattr in the same patch), second ‘getpatcher’. But first it responds to getpatcher and second to getVar.

Does anyone have a clue?

Thanks,
Mattijs

#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P newex 91 25 74 9109513 loadmess value;
#P newex 91 46 44 9109513 pattr Var;
#X prestore 1 0 value;
#P objectname Var;
#P newex 122 143 26 9109513 print;
#P button 90 79 15 0;
#P newex 90 97 88 9109513 t getpatcher getVar;
#P newex 90 121 42 9109513 pattrhub;
#P connect 5 0 4 0;
#P connect 0 1 3 0;
#P connect 2 0 1 0;
#P connect 1 1 0 0;
#P connect 1 0 0 0;
#P window clipboard copycount 6;


September 24, 2006 | 7:47 pm

I can’t reproduce this. Max 4.6.2, MacOS 10.4.7 PPC.

jb

Am 24.09.2006 um 21:36 schrieb Mattijs Kneppers:

> Hi, I am troubled by a strange problem. The patch below illustrates
> it.
>
> I send pattrhub two messages, first ‘getVar’ (referring to a pattr
> in the same patch), second ‘getpatcher’. But first it responds to
> getpatcher and second to getVar.
>
> Does anyone have a clue?


September 25, 2006 | 8:04 am

On 24 sept. 06, at 21:47, Jeremy Bernstein wrote:

> I can’t reproduce this. Max 4.6.2, MacOS 10.4.7 PPC.

me neither. (same config)

ej


September 25, 2006 | 8:48 am

Oh? hmm.. maybe a 4.5 thing? I tried with Max 4.5.7 on windows XP and with Max 4.5.7 on Mac OS 10.4.7

My output is:

print: patcher this
print: Var value


September 25, 2006 | 9:14 am

I have the same results with Max457 under OSX.3.9 !!

On 25 sept. 06, at 10:48, Mattijs Kneppers wrote:

> Oh? hmm.. maybe a 4.5 thing? I tried with Max 4.5.7 on windows XP and
> with Max 4.5.7 on Mac OS 10.4.7
>
> My output is:
>
> print: patcher this
> print: Var value

_____________________________
Patrick Delges

Centre de Recherches et de Formation Musicales de Wallonie asbl

http://users.skynet.be/crfmw/max


September 25, 2006 | 8:06 pm

Additionally (maybe the same problem?), the ‘patcher’ message is not processed in sync when loading a patch.

When I load the following patch I get
print: patcher this
print: patcher this

When I then send the message ‘getpatcher’ manually I get
print: patcher parent::linkToHere

When you manually doubleclick the loadbang in the patch after setting patcher back to ‘this’. I get what I would have expected:

print: patcher this
print: patcher parent::linkToHere

Max 4.5.7, windows XP (didn’t try this last one on Mac OS yet)

Is there an explanation and/or workaround for this (without using deferlow)? I really need this functionality. I want to use pattrhub to check if a patch exists. To achieve this I first set patcher and subsequently use getpatcher and see if pattrhub accepted it.

Thanks,
Mattijs

#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#N vpatcher 802 415 1095 677;
#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P message 127 96 57 9109513 patcher this;
#P message 127 75 52 9109513 getpatcher;
#P newex 15 33 45 9109513 loadbang;
#P newex 15 75 110 9109513 t getpatcher l getpatcher;
#P newex 47 135 26 9109513 print;
#P message 15 54 118 9109513 patcher parent::linkToHere;
#P newex 15 113 42 9109513 pattrhub;
#P objectname u672000002[1];
#P connect 4 0 1 0;
#P connect 1 0 3 0;
#P connect 6 0 0 0;
#P connect 5 0 0 0;
#P connect 3 2 0 0;
#P connect 3 1 0 0;
#P connect 3 0 0 0;
#P connect 0 1 2 0;
#P pop 1;
#P newobj 3 53 70 9109513 p pattrhubHere;
#N vpatcher 897 197 1073 380;
#P pop;
#P newobj 3 30 60 9109513 p linkToHere;
#P objectname linkToHere;
#P window clipboard copycount 2;


September 25, 2006 | 8:38 pm

Pfew!! Pattr’s bindto message hasn’t got the bug! :DDD
I’ll be able to what I wanted after all!


Viewing 7 posts - 1 through 7 (of 7 total)