Quoting "Jonathan Wilkes" <[email protected]>:
I don't think writing a self-documenting patch and the use of iem gui objects are mutually exclusive; after all, I use iem guis in the example patch you are referring to. It's just that for the particular behavior of linking two iem guis, I wouldn't rely on whatever it is that happens when you make all the send/receive names the same. Instead, I would use something like the "explicitly patched" version and shove it all in a gop. Then if you decide after many months that you want to send a value to one of the iem guis, for example, and have all the linked iem guis update their values, it will work (and you can easily check for bugs by opening the gop window). If you try the same thing with the send/receive name trick, it will fail, and if you're like me and have a hard time reading the source code, then there's (currently) no quick way to figure out why it doesn't work because it's not documented in the help patches for the iem guis.
the send/receive "magic" in the iemguis are explicitely designed to allow the same send/receive names in order to sync several different objects.
of course you can do this explicitely. iemguis just help to make this simpler. mfgasdr IOhannes ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
binKKBZ4OEUpB.bin
Description: Öffentlicher PGP-Schlüssel
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
