Roman Thilenius

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,

even when the offset message is produced in root (fopr example

does not work = weird drawing problem, old stuff isnt refreshed.

whats up? bpatcher refreshes fine when offeset from root, but not

offeset message, coming from _another bpatcher = does not work,
even when the offset message is produced in root (fopr example
by triggering a messagebox).

whats up? bpatcher refreshes fine when offeset from root, but not
when mouse is inside another bpatcher?

bpatcher2bpatcher-messages

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:

- A way to see only part of a subpatcher in a patch without having to use a separate file.

- An option that makes the top left corner of a bpatcher the origin (0,0) when moving objects around using thispatcher.

https://cycling74.com/forums/index.php?t=msg&goto=94703&rid=5118&S=94f71fc2118610c7bb2bf6ddc7a9ce97&srch=bpatcher#msg_94703

https://cycling74.com/forums/index.php?t=msg&th=25207&start=0&rid=5118&S=94f71fc2118610c7bb2bf6ddc7a9ce97

Let's hope Cycling finds the time to solve these problems and possibly add to the functionality of the bpatcher object:
- A way to see only part of a subpatcher in a patch without having to use a separate file.
- An option that makes the top left corner of a bpatcher the origin (0,0) when moving objects around using thispatcher.

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

a drawing (i.e. refreshing) problem - yet i solved putting 

a [pipe 0] into the controlling bpatcher. (like we are used

to solve the common initialisation order problems.)

i guess its to do with the mouseclick (in an [lcd], but

it does not seem to matter), however its weird.

i am not "including", but i second your request about 
"unincluding".

if we had that, maybe i would finally see some sense in
"including" bpatchers? :)

btw this is mac os classic - so it seems a persistent
problem.

funny thing is, i am 100% sure now that it is realy only
a drawing (i.e. refreshing) problem - yet i solved putting 
a [pipe 0] into the controlling bpatcher. (like we are used
to solve the common initialisation order problems.)

i guess its to do with the mouseclick (in an [lcd], but
it does not seem to matter), however its weird.


> I'm able to copy the behaviour you described. I've included the 

Thanks, elsewise nobody else would have jumped on it

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

I am sure you came across this before, it just looked different. Its the 

same reason as all the other bpatcher problems: redraw. If you send max 

a redraw command after the offset message, it will display correctly...

Bas van der Graaff schrieb:
> 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.

I am sure you came across this before, it just looked different. Its the 
same reason as all the other bpatcher problems: redraw. If you send max 
a redraw command after the offset message, it will display correctly...

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


bpatcher2bpatcher messages