On Sun, Jul 15, 2007 at 10:41:13PM -0400, Chris McCormick wrote:
On Sun, Jul 15, 2007 at 03:18:05PM +0200, Derek Holzer wrote:
This is fairly esoteric to me. Could you give a real world example of
what such an object would be used for? What need does it fulfill in your
own patching
On Mon, 16 Jul 2007, Chris McCormick wrote:
I can't answer for matju, but it seems like this would be useful for
making sure your signal paths are connected and data is flowing in the
way that you expect. This should be obvious by reading the patch, but
in a very complicated patch it could be
This is fairly esoteric to me. Could you give a real world example of
what such an object would be used for? What need does it fulfill in your
own patching strategies? Why did you make it?
best,
d.
Mathieu Bouchard wrote:
using a [tracecall] object you can trace back the original cause of
On Sun, Jul 15, 2007 at 03:18:05PM +0200, Derek Holzer wrote:
This is fairly esoteric to me. Could you give a real world example of
what such an object would be used for? What need does it fulfill in your
own patching strategies? Why did you make it?
I can't answer for matju, but it seems
using a [tracecall] object you can trace back the original cause of
messages. see:
http://artengine.ca/desiredata/gallery/tracecall-help.png
notes:
[message] is the messagebox class
[message] uses [messresponder] to send messages
[__manager] represents the mouse click
_ _ __ ___
