Not going to do the same thing for rescue @jtbui20 , the code for that is way too ugly.
I think the best way to move forward is:
Soccer:
This preset (and rescue) were made before pygame_gui was added to the project. Since then adding UI to the presets has been made a lot simpler, see for example the code in https://github.com/MelbourneHighSchoolRobotics/ev3sim_custom_presets/blob/main/colorSensing/preset/preset.py (Some of the boilerplate in there around button theming can be removed but i cbf. So it's probably best if we do redesign soccer to build the ui from scratch using the new system.
Rescue:
That entire script is just one big prototype, so once you are ready lets discuss on paper or whiteboard what you want the ui to be / how it should function, then I can help rewrite that mess (And you can write the ui portion in a file similar to ui.py in this PR).
Not going to do the same thing for rescue @jtbui20 , the code for that is way too ugly.
I think the best way to move forward is:
Soccer: This preset (and rescue) were made before pygame_gui was added to the project. Since then adding UI to the presets has been made a lot simpler, see for example the code in https://github.com/MelbourneHighSchoolRobotics/ev3sim_custom_presets/blob/main/colorSensing/preset/preset.py (Some of the boilerplate in there around button theming can be removed but i cbf. So it's probably best if we do redesign soccer to build the ui from scratch using the new system.
Rescue: That entire script is just one big prototype, so once you are ready lets discuss on paper or whiteboard what you want the ui to be / how it should function, then I can help rewrite that mess (And you can write the ui portion in a file similar to
ui.pyin this PR).