That took much less time that I thought. Switches are working, at least basically. The modules on the right are LEDs. The top left module is a button. The bottom left module is a switch.
This movie requires Flash Player 9
My attempt at updating NeatTools (C++ and AS3)
That took much less time that I thought. Switches are working, at least basically. The modules on the right are LEDs. The top left module is a button. The bottom left module is a switch.
I don’t understand the inputs to the lower indicator, the one connected to the switch and pushbutton. It lights with the switch on, and turns off with the pushbutton once on. The logic is apparently toggle the indicator state with a change of any input to 1. In practice, inputs should be ORed or ANDed. In the first case, the indicator lights if any input is 1. In the latter case, the indicator light only if all inputs are 1.
Otherwise, bravo!
Damn. You’re right, of course. So for now, it’s not NeatTools compliant. I modeled what I’m trying to do in NeatTools and I don’t understand the NeatTools behavior, so good luck to me trying to replicate it. In NeatTools, if you click the button, they both light, then if you click the switch, the bottom ones stays lit, then if you click the button again, they are both lit, but when you let go, they both go off.
I’ll keep at it.
You are right. NeatTools does it “wrong”. I suspect that this has to do with the broadcast model. In the NeatTools case, only the line with a data change event is being evaluated.
I contend that this is wrong. Any input data change should precipitate a reevaluation of ALL the inputs.
I also think that multiple inputs should either be ORed or ANDed, as I’ve said before. It might be interesting to be able to select the desired behavior, but it should adopt one or the other behavior. I suggest that OR should be the default. Maybe it’s just my inner ECL logic designer emerging…