[2.1.7] Enabling both "Set recipe" and "Read ingredients" on an assembling machine causes rapid flickering of the recipe

[dmitmel]

Steps to reproduce:
1. Build an assembling machine (or any crafting machine for that matter)
2. Connect it to a circuit network, and tick both "Set recipe" and "Read ingredients" options for this machine
3. Connect it to something that sends a signal, such as a constant combinator, use it to send a signal for a recipe whose ingredients are also valid recipes (e.g. green circuit, which takes copper wires, which are also crafted in assembling machines)
4. Observe rapid flickering of the recipe selected by the machine.

I suspect this is caused by the recent changes to the circuit network since it's now possible to select which of the two wires act as inputs/outputs. However, the old behavior in that the machine would ignore the signals which it itself sends out is very useful, e.g., I use it in an auto-mall design: I feed the recipe on the green wire into an assembler, have it output its contents, read them on the red wire, which is not contaminated with the signal which sets the recipe, but use both wires to access the working/finished status flags of the machine on both the green and the red wires, which are connected to surrounding combinators which are necessary for the auto-mall to work. I would kindly ask that you consider bringing back this old self-subtraction behavior, which, in addition to the input/output selection checkboxes would be a killer combo.

[boskid]

Thanks for the report. Everything here works as expected - assembler sends ingredient signals onto a red wire and tick later assembler sees those signals appearing on red wire and changes recipe as requested.

Old behavior was based on magic self-subtract which is gone. If you want to make outputs not influence inputs, you can use checkboxes near input and output line to select which wires to use such that ingredients are sent to a different wire.