Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

schedulemessage clear content? #18

Open
HansElectrumpet opened this issue Nov 18, 2022 · 3 comments
Open

schedulemessage clear content? #18

HansElectrumpet opened this issue Nov 18, 2022 · 3 comments

Comments

@HansElectrumpet
Copy link

Hi Alex,

It is very nice to see the updates on the objects. I have just discovered schedulemessage and I was wondering if it is possible to clear future events from schedulemessage, like pipe has both the 'flush' method and just 'clear'. I could not find it in the code, so maybe this counts as a feature request?

Thanks.

Best, Hans.

@AlexHarker
Copy link
Owner

This doesn't currently exist - I'm not sure how difficult it would be to add - I think pipe might have it's own scheduler, which to my recollection schedulemessage does not currently, but I can certainly keep it here for consideration.

Out of interest - what is the sort of use case that you had in mind for this feature?

@HansElectrumpet
Copy link
Author

Hi Alex,

Thanks for the quick reply. In my case the idea would be that I start a sequence of events but that I would also be able to cut off at any given moment. When then starting a new sequence again, I don't want any messages still in the pipeline disrupt this new sequence.

Those messages are OSC-messages with their parameters. I have found a workaround by converting the message and parameters to a symbol and then delay them with pipe and converting them back.

Best, Hans.

@AlexHarker
Copy link
Owner

Yes - that makes sense. No promises on when but this seems worth including if I can at some point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants