Forums > MaxMSP

picture and bpatcher overlapping issues

December 12, 2010 | 1:01 pm

once more i´ve run into a situation where OSX differs from OS 9.

i am script-creating and script-deleting a background-picture (using
the picture object) in a patch which has visible bpatchers and some
regular objectboxes in it.

in OS 9 the scrript does the following:

1. deletes the picture, in case there still is one.

2. creates the picture

3. puts the picture to background

after the script has been triggered, i send a refresh message to max in order to
get rid of the – more or less natural – drawing problems.

the refresh message happens right after creating and moving the picture to
background via [t b b]

in max 4.6 OSX this does not work … the refresh message seems to vanish,
only when you trigger it manually, the diplay errors disappear and the desired
state of the patch is reached.

strange enough, in max v5 my 4.1 code works perfectly (it is even smoother than in
4.1) – just not in 4.6.

i am not asking a for a solution for such strange requests of mine, but how come
that a message from a t b b obviously vanishes in max 4.6, but works in max 4.1?

shouldnt scripting a picture object be identically in these two versions of the runtime?


December 12, 2010 | 2:03 pm

Forgive me for asking the obvious: deferlow?


December 12, 2010 | 2:23 pm

i could try that.

the three or four classic users need to install a deferlow dummy then, but it could work.

December 12, 2010 | 2:37 pm

Hmm, that’s a real dilemma. But did qmetro exist back then?

— Pasted Max Patch, click to expand. —


December 12, 2010 | 4:28 pm


but i can just do t b b b with one more b, one for refreshing normal and one for refreshing with deferlow.
that will exactly work and doesnt even trigger double in classic, where the deferlow object is out of order.

i have yet to test if it help.

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

Forums > MaxMSP