Roman Thilenius

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

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

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

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

strange enough, in max v5 my 4.1 code works perfectly (it is even smoother than in

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?

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.

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?

picture-and-bpatcher-overlapping-issues

Forgive me for asking the obvious: deferlow?

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

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

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.

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.

picture and bpatcher overlapping issues