Is your feature request related to a problem? Please describe.
When launching the engine visualizer, some features can be hard to see due to low contrast.
Describe the solution you'd like
The engine visualizer should have the same contrast values as the main GUI's axes. This should also update in real-time as the user modifies the manual contrast values. Ideally, this would result from method calls in a separate engine visualizer class.
Describe alternatives you've considered
Could just pass the CLim property from the GUI axes to the engine visualizer upon launch and whenever the UpdateEngineVisualizer property is called. Could also consider passing a reference to the GUI's axes and linking the CLim property between the axes of the last plot in the engine visualizer and the GUI's axes. This would simply require calling the linkprops function
Is your feature request related to a problem? Please describe. When launching the engine visualizer, some features can be hard to see due to low contrast.
Describe the solution you'd like The engine visualizer should have the same contrast values as the main GUI's axes. This should also update in real-time as the user modifies the manual contrast values. Ideally, this would result from method calls in a separate engine visualizer class.
Describe alternatives you've considered Could just pass the CLim property from the GUI axes to the engine visualizer upon launch and whenever the UpdateEngineVisualizer property is called. Could also consider passing a reference to the GUI's axes and linking the CLim property between the axes of the last plot in the engine visualizer and the GUI's axes. This would simply require calling the
linkpropsfunctionAdditional context An example of the issue...