Issues with event.addToSequencer() while the sequencer is running about mwengine HOT 5 OPEN

I've gotten around this by adding the events to the sequencer on creation and the never remove them, just enable/disable. Is this how it's supposed to be handled?

from mwengine.

Hm, no that seems properly broken 🙈

I think what is going is that the events are not added to the currently running sub-sequence cache (explaining why your experiment with the timeout seemed to work). I'll have a look.

(If you are testing with (Base)SynthEvents, it may be possible that the bug you highlighted in issue #146 may be the culprit)

from mwengine.

The problem is still there with the latest build.

from mwengine.

Would you have some (pseudo) code relating to all operations you do with an event when you both add and remove them when clicking on the cell pads ? I can't quite reproduce and am wondering whether the sequence of things might be an issue (I'm curious whether you also set the event position prior/after addition to the sequencer or something related).

from mwengine.

If the event is off when clicked, event.addToSequencer() is called, and the other way around. Logs show them to be called in the right order at the right time etc.

from mwengine.