You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if a single argument changes in the configuration, the entire gauge is rerendered. E.g. every time the value changes, not only the pointer is updated, but all axes, segments, ticks, etc. are rerendered. This is obviously very resource-intensive.
Splitting the rendering of different elements like the segments, ticks and pointers to different render elements like RenderRadialSegment, RenderRadialTicks and RenderRadialPointer and only rendering after changes might improve the performance. Currently, all elements are rendered by a single RenderBox: RenderRadialGauge.
The text was updated successfully, but these errors were encountered:
Currently, if a single argument changes in the configuration, the entire gauge is rerendered. E.g. every time the value changes, not only the pointer is updated, but all axes, segments, ticks, etc. are rerendered. This is obviously very resource-intensive.
Splitting the rendering of different elements like the segments, ticks and pointers to different render elements like
RenderRadialSegment
,RenderRadialTicks
andRenderRadialPointer
and only rendering after changes might improve the performance. Currently, all elements are rendered by a single RenderBox:RenderRadialGauge
.The text was updated successfully, but these errors were encountered: