Well, it's full of [trigger]s..
On Tue, Jan 8, 2013 at 8:25 PM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2013-01-08 19:18, Alexandros Drymonitis wrote:
No, that's not the case. I've actually never really touched the example patch. Anyway, my actual worry is why these objects behave the way they do in my patch, which is really strange. In order to see what's wrong I opened earlier versions of the patch I'm working on (which were using [link] and [mass] fine) and they also show the same strange behavior. It looks like a bug hit it all of a sudden.. I've attached an earlier version which is smaller, if anyone's willing to check. Physical modelling is inside [pd object1], [pd object2] etc. inside [pd coordinates1].. It used to be that the first time you hit the bangs, the rectangles wouldn't behave as expected (in the gem window), but after that everything was working pretty stably. Hope someone can help.
i haven't really tried to understand your patch, but you will most likely find, that [trigger] will fix most of your problems.
**never ever connect one message outlet to multiple message inlets; always use [trigger] in such cases**
fgmasdr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlDsZIkACgkQkX2Xpv6ydvSLjACfSdq5S3d5gfewhHix9ZOJhLJ2 ftEAoLwwKnhAX68HaLw1qItWOW3zl6a6 =O2gO -----END PGP SIGNATURE-----
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list