I’m trying to do the following : I have an event A that will fire at some point, but I want to hold it until another event B fires.
Idea is that my application will receive some notification from the outside telling it to do something, but I need to delay that something until another event, internal to my application, allows that something to happen.
I have found a solution looking at some C# stuff online and came up with the following weird patch. It does what I want, but it looks.. funny.
Here’s a patch and a video recording. Is there something
So, rather than trying to understand Reactive events I have never used, I tried to patch the thing manually and came up with this DelayUntilOnce node. Difference with the previous setup is that it allows the event to be re-emitted only once, which I needed for my use case.
I did it with a SpreadBuilder but I guess there are better structures like Queues to do those things.
If someone knows a thing that already does that off the shelf please let me know :-)
In the case of Zip, there will be a buffer, and the event will be saved as many times as it is called, and each call on the right will retrieve from this buffer.
Still a bit lost with all these Reactive operators. I indeed have to manage a state since the event should be allowed to fire just once, which I did in my previous post with a SpreadBuilder. Maybe not super elegant, but works :)
Observables should have a WithLatesFrom function, which should essentially allow you to continuously receive the latest value from stream A through events in stream B. But I don’t see it in the VVVV API. But maybe it’s just CombineLatest node
