Egui Uppdate and simulator state to keep track of component condition

[Spooky-Firefox]

Egui were updated to 0.28.0

egui were updated to 0.28.0, required moving where clock() were called
as the preprocessing previous used have been deprecated. other changes where minor

Simulator State

Overview

State were added to simulator, allowing to set state to StepTo making the simulator automatically stop when a cycle is reached.
It also track if an halt, assert or error occurred during clocking the simulator.

compoennt codition vector were added allowing to se what may have caused a change in running state

GUI

Both simulator state and Componente condition vector were incopretaed into the ui

Changes

Two simulator fields were added and one changed

• running -> running_state
  • Used to track if its running, halted, steping to a cycle or a Error ocured
• component_condition
  • Used to keep track of what condition where reported during current cycle
• halt_on_warnings
  • If simulation should halt if a components reports a warning

Two struct were created, RunningState and SimulatorError. RunningState enum can be running, stepping, stop, halt, assert or error. and SimulatorError enum is currently not fully implemented but is returned if clock or other function tries to run when state is error.

The Clock function were changed to update state and track component condition. This was done by adding all conditions reported to the vector and get the max Condition of the said vector, using derived compare on condition. The max condition is used to update state to an appropriate value.

some changes in gui were made to add the buttons and labels winch show state and reported conditions.

Misc

• Default fern setup was changed to stop reporting when a redraw happens.
• Updated tool-tip for probe

[onsdagens]

hi, i've fixed up the vizia build, let's see if CI passes.

[onsdagens]

Seems locally building the RISC-V model also fails, i will also fix that.

[onsdagens]

Seems good now. As a side note, we should add the RISC-V model (and the MIPS once that's merged) to the CI build and clippy tests.

What about the TODO's? Should we merge this as is or does it need more work first?

[onsdagens]

After IRL discussion, the TODOs have been handled. LGTM!