Hi,
Signals are the go-to way to handle simple state, but the one-action limit per rule often leads to extra “signal only” rules, or using Stored Values as basic flags.
Could we allow setting or clearing more than one signal per rule trigger?
This would reduce clutter, keep common workflows signal-led, and is especially helpful for newer users who are better off staying with signals before diving into SVs.
If each change still writes its own market log line, debugging stays clear.
Is there a technical reason it must stay as one signal action per rule?
Allow setting or clearing multiple signals per rule
- jamesedwards
- Posts: 5119
- Joined: Wed Nov 21, 2018 6:16 pm
Not voting as I never use Signals. Unless I'm missing something I don't see the point when Stored Values do the same thing but offer much greater flexibility.
Fair point. I use Stored Values for pretty much everything, so it’s a bit ironic I’m the one posting this.
This isn’t about how I work now, it’s about newer users. When I started, signals felt much easier than SVs, and this would help them avoid a bunch of “signal only” rules while they’re still learning.
This isn’t about how I work now, it’s about newer users. When I started, signals felt much easier than SVs, and this would help them avoid a bunch of “signal only” rules while they’re still learning.
