Mar 23, 2007 at 11:05am
offset message, in bpatcher, to [thispatcher] of bpatcher = works
offset message, from root, to [thispatcher] of bpatcher = works
offeset message, coming from _another bpatcher = does not work,
does not work = weird drawing problem, old stuff isnt refreshed.
whats up? bpatcher refreshes fine when offeset from root, but not
Mar 23, 2007 at 1:25pm
I’m able to copy the behaviour you described. I’ve included the sample patch that I made below. Unexpected behaviour, since the message does seem to reach the correct bpatcher object, and it does work if you trigger the message anywhere else. Luckily I haven’t come across this before.
It’s too bad that the bpatcher object is recently (at least, to me) showing some weird behaviour, especially since it is one of the very few ways to make a more complicated interface in Max.
Let’s hope Cycling finds the time to solve these problems and possibly add to the functionality of the bpatcher object:
Other recent bpatcher problems:
#P window setfont “Sans Serif” 9.;
Save as ‘bpatch1′:
#P inlet 23 28 15 0;
Save as ‘bpatch2′:
#P toggle 17 27 15 0;
Mar 23, 2007 at 1:47pm
Mar 23, 2007 at 2:55pm
Mar 25, 2007 at 8:50am
i am not “including”, but i second your request about
if we had that, maybe i would finally see some sense in
btw this is mac os classic – so it seems a persistent
funny thing is, i am 100% sure now that it is realy only
i guess its to do with the mouseclick (in an [lcd], but
Mar 26, 2007 at 4:28pm
Bas van der Graaff schrieb:
Thanks, elsewise nobody else would have jumped on it
> Unexpected behaviour, since the message does seem to reach the
I am sure you came across this before, it just looked different. Its the
You must be logged in to reply to this topic.