On Aug 11, 2007, at 3:23 PM, pd-list-request@iem.at wrote:
For now you could also schedule a "stop" message to [writesf~] with a [delay <maxlength>] object that's bang'd whenever you "start"
recording.Wrap this it into an abstraction and you should have your feature request fulfilled.
Thanks. That's what I'll do. Also, the control to "stop" the
recording must also send a stop to cancel the delay. Failing to do
so could lead to some very hard to debug behavior.
(---o-------o-o-o---o-o-o----( David F. Place mailto:d@vidplace.com
Thanks. That's what I'll do. Also, the control to "stop" the recording must also send a stop to cancel the delay. Failing to do so could lead to some very hard to debug behavior.
That might not be necessary. The delayed 'stop' message only comes after the most recent message. If multiple messages are sent within the delay time, then only the last one matters.
So, I think, the worst that could happen ( in a series of bang/stop messages) is a redundant stop message, which I assume does nothing.
Chuck
On Aug 11, 2007, at 4:22 PM, Charles Henry wrote:
That might not be necessary. The delayed 'stop' message only comes after the most recent message. If multiple messages are sent within the delay time, then only the last one matters.
So, I think, the worst that could happen ( in a series of bang/stop messages) is a redundant stop message, which I assume does nothing.
Thanks. I was easily able to create a patch that confirms that
behavior.
(---o-------o-o-o---o-o-o----( David F. Place mailto:d@vidplace.com
-
Charles Henry -
David F. Place