Delay bug
Hi, I teach an intro to Max course at a university and was helping troubleshoot a student's patch when I realized that the delay object has a small bug.
The student had accidentally hooked up a toggle to a delay object set to 1000ms. When activating the toggle, the delay sent out a bang immediately. When I instructed him that the delay object accepts bangs in the left inlet, he hooked up a button, but the delay object was still sending out a bang immediately.
It turns out that if you send a number into the LEFT inlet of delay, it actually sets the delay time. This means that by hooking up a toggle to the delay and activating it, he was setting the delay time to 1ms. This is not documented anywhere and did not output an error in the Max console. Just thought I should post this here so it could be fixed.
I actually don't think this is a bug. It's actually useful. An int on the left triggers a bang with that delay amount, an int on the right just redefines the delay value without any output.
When you put it that way, I can see the value. So perhaps the documentation just needs to be updated to reflect that the delay object can receive an int on the left side that behaves in this manner.
Nevermind, it IS documented! Always read the help file. My apologies.