maybites

I just noticed to my surprise that a delayed bang has a different effect than a mouse triggered bang:

if you look at this example patch - you can trigger the shared - message directly - or via bang - in both cases the print object will show the created message sent to the jit.window object, but only the one triggered by mouse is actually causing the jit.window object to react - i.e. to quickly flash.

can anybody tell me what is going on here?

delay-bang-is-different-than-mouse-triggered-bang-why

freaky. I'd like to know more about this too...I thought a bang was a bang was a bang...

I think it's a matter of event priorities. Try inserting [deferlow] after [delay].

https://cycling74.com/articles/event-priority-in-max-scheduler-vs-queue/

deferlow does actually the trick - thank you.

max once more looks like a dark pit with unknown secrets...

[defer] should be enough to get something [delay]ed back to the main thread.

delay bang is different than mouse triggered bang - why?