You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At each tick, the value corresponding to the current input will be sent.
If I want to somewhat prevent this behaviour, I can set a repetition filter.
However now I will get a new value only when the current value changes.
Would it be possible to rework the general TimeProcess API so that Process can instead depend of incoming messages ?
i.e. when I get an input on a message /foo and my mapping does map /foo to /bar, I want to get a message in /bar, whatever the message is in /foo side.
The text was updated successfully, but these errors were encountered:
Today, if I have a process such as a mapping :
At each tick, the value corresponding to the current input will be sent.
If I want to somewhat prevent this behaviour, I can set a repetition filter.
However now I will get a new value only when the current value changes.
Would it be possible to rework the general TimeProcess API so that Process can instead depend of incoming messages ?
i.e. when I get an input on a message
/foo
and my mapping does map/foo
to/bar
, I want to get a message in/bar
, whatever the message is in/foo
side.The text was updated successfully, but these errors were encountered: