13-05-2021, 12:29 PM
(13-05-2021, 08:38 AM)josemendez Wrote: I agree that I should probably check for this in-editor and place a warning in the updater or just refuse to run the simulation if the user adds the same solver twice, though. Won't catch the case where different updaters update the same solver, but at least it will warn about the single updater case. Will do in the next update.
I suppose you could have solvers and updaters mutually keep references. When a solver is told to be added to an updater, the updater will check the solver's stored updater. If it is non-null, it tells you about it and/or refuses to add the solver to the updater, or removes it from the first updater. Not sure if the overhead involved in this check would outweigh the extra robustness to user error.