max 7.2.5 #0 wildcard de-encapsulation


    Oct 12 2017 | 8:36 pm
    Hi,
    I've noticed a bug: when I de-ecapsulate a sub-patch containing an object that uses the #0 wildcard, if that sub-patch was locked at the time, I end up with a version of the object with the #0 permanently substituted.