picture and bpatcher overlapping issues
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?
Forgive me for asking the obvious: deferlow?
i could try that.
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?
----------begin_max5_patcher---------- 565.3ocuVssaiCBD8Y6uBDOmsx.wW59grurpJhXSSXUL1KFqlsU8eubwdaSa tfqu7PBhISFNy4Ly.uDF.2Vcj0.A+D7aPPvKgAAVSFCAc6Cfkzi4GnMV2fB1 SUa+Cbk6mTriJq4ZIWn.0UsxM46ok0T9NQuSOVITM7mYFGQn6h5LKZK4hCLk MtnNi7Ba3zGwOPIeL.BZoM.vewjETAE9dTpZU8goO10TU9dtX2FIKW4RObxZ 8QCHQQlEDgXVv5MfGL+mWCCMesxSZXaqRUIf9lJwmGt8t5Lo9WMygU3VpXGD 7vUxFThA+IQ8YwHxkKHoJ.BDMVMjLbMDeIRQWgAW4V7fZxbxc5bPMtpcI6QI qY+XoH7zVlu1VLPv1zO894K8Kjzm1TyyUsR1X4.zzxAtJ.x5LaqNBOOsGis4 Hc3IM5Z8FWsoH0RI3XGWjLGLRC6.HROz.CHijY9FSMhu5nzUWd0mYIn6szVJ YNns7pVghIGBkE+UJ6aLEY8MFz1+wyAtnjr4ij9aISIqFVKG9LCZlvVNeuiF QrEOInyxK1..OvEe9YX1.ZreJY0nehUdOD55U.j+CiBVihKnJt9wIu6idRit yr2m87hBl3iyPK4E0UZYtCBWP37EQmdZmGQnggHbV7cwZ1Kyc4Fwd41o6PQt 65vVOs6FYdf7HOvKJyZdN0TSsiDRFDguEhRFnZqukxn1SgFF6CiQVdUD4QgE dQUwagHDdwKrtovsr05XOfzXJkzadM7MYFwjL. -----------end_max5_patcher-----------
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.
Forums > MaxMSP