Gax
Simulating electricity flow in wire/component classes in a linked list like manner
I was asked to use a base class for all components so that creating new components as they need is easy, since I'm only responsible for the main "flow from A to B correctly" part of it
11 replies
Simulating electricity flow in wire/component classes in a linked list like manner
I'm mostly treating the wire class as both that and a base component class.
Even when rewriting to fit that idea, I'd still be faced with the same issue: I still would need to figure a way to examine and find where the "beginning" of the circuit is
Unless I'm having a bad case of tunnel vision I can't see how refactoring to use nodes and wires would help finding that
11 replies
Simulating electricity flow in wire/component classes in a linked list like manner
I have looked into them, a small amount are open source and while they use a slightly similar approach, the ones I found seem like their own implementation of it
The reason I have
Wire is for more easily implementing the components without having to repeat a lot of behaviour, and having the "universal" changes apply to them (like the normal flow of electricity and such)
While a resistor inheriting from a wire might sound weird, all that would mean is that it would inherit the same properties like position and colors and such, while also following the basic flow that wires do, with the added change of passing less voltage through11 replies
Generating input fields for each element in an array in Blazor WASM
I've solved it by just making a class purely to serve as a "reference type array" and using it instead of just the default array, not the best solution but for my use case is good enough I guess.
All it has is a private array field to store the values and an indexer which is all I need
I also made an input field component that has parameters to store the reference to that object and an index representing which value to change
6 replies
