simulation: Replace the current timer-based system for Component Updates with a notification-based system that only updates components when an input changes

[d-khalid]

What to change

• The current system for updating the outputs of components. It uses a dispatcher timer that updates every component and wire every after X amount of time. It is to be replaced with a different approach, each component updates (runs its ComputeOutput() ) if there is a change in the value held by one of its inputs.

Why does it need to change

• The current approach wastes compute on recomputing outputs on the exact same set of inputs. It also creates timing issues with clocks, for example there can be cases where the circuit updates happen only on the low part of a clock pulse, creating unintended behaviour making the clock act as a constant low signal

Contributing

If you want to get this issue assigned to you. Just comment I want to work on this issue. You will be assigned to the issue instantly via GitHub-actions bot.

Also please use IDE-integrated LLMs responsibly. LLMs output low quality code (redundant, not clean, not scalable and so on) and such PRs will be turned down without warning.

[ShahzaibAhmad05]

take the guinness world record for the longest issue name ever crafted

[d-khalid]

Next time I'll copy paste the entire vaporeon copypasta in there :p

[ShahzaibAhmad05]

I want to add something. the input terminals are null when the object is created, and assigned in the object initializer. For a gate it would be something like this:

GateViewModel gate = new() { Input = new(), Output = new() };

basically when these pins get assigned then you have to intercept the call and make the pin (PropertyChanged) subscribe to a function that allows compute output which is named Simulate(). The other thing would be removing the simulation dispatcher timer and all its refs

[ShahzaibAhmad05]

this ive typed is just an outline, there are alot more details to this