Report this content
We want the Dreams coMmunity to be a safe, diverse and tolerant place for everyone, no matter their age, gender, race, sexual orientation or otherwise. If you believe this content to contradict these principles, you can file a report for our coMmunity teams to investigate.
Note that misuse of the reporting tool will not be tolerated.Item being reported:
If a signal is wired into a setting, it should always be setting the value of that setting. That's how it works in all circumstances, apart from the active port on a selector.
While the active port is being set to "2," if a value wired into port 0 (A) goes from non-positive to positive (eg. 0 to 1) it will flicker to port 0, and then back to port 2. This is unexpected and unintuitive behaviour. And there's no reason you'd want it to work like this.
It's been reported as a bug for years now, but with no fix unfortunately; maybe it's technically *meant* to work like this, despite it not making sense. So I thought I'd suggest it here as a new feature, or change to the selector...
While the active port is wired into, it should override all other methods of changing port. Inputs to a channel and inputs to next/previous should be completely ignored for the purposes of changing the port.