note also that merely loading [propertybang] is disabling the properties menu item on every GOP in its parent patch except the ones that use [propertybang]...
note also that [propertybang] writes to a global variable in a way that no other external can compete with, apparently...
i'd very much like to use [propertybang] or code something similar to it, but I'm not very comfortable with some things that it does.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
On 2010-04-01 03:18, Mathieu Bouchard wrote:
note also that merely loading [propertybang] is disabling the properties menu item on every GOP in its parent patch except the ones that use [propertybang]...
note also that [propertybang] writes to a global variable in a way that no other external can compete with, apparently...
i'd very much like to use [propertybang] or code something similar to it, but I'm not very comfortable with some things that it does.
sure, any help is welcome.
fgmasdr IOhannes
PS: is it just my broken thunderbird that fails to put your answers into the correct thread (or any thread at all) or is there a reason why alpine does not add any "in-reply-to" or "references" fields?
On 2010-04-01 16:26, IOhannes m zmoelnig wrote:
On 2010-04-01 03:18, Mathieu Bouchard wrote:
note also that merely loading [propertybang] is disabling the properties menu item on every GOP in its parent patch except the ones that use [propertybang]...
fixed now (as far as i can)
note also that [propertybang] writes to a global variable in a way that no other external can compete with, apparently...
that's the unfortunate way how Pd handles classes. i would love it, if each instance would actually have a copy of the class data, rather than all instances pointing to the same class data.
i'd very much like to use [propertybang] or code something similar to it, but I'm not very comfortable with some things that it does.
is it better now?
fgmasdr IOhannes