Let's make it so graphics from 1 widget don't bleed out of the bounding box of their widget container!
Often times, the circular vizualizers in the EMG Widget and others will expand out and render over other widgets / graphics.. Buttons also do this to each other somtimes.
Describe the solution you'd like
This isn't an easy problem, but figuring out how to make it so all widget rendering functions are aware of their own rendering limitations, and then snip/crop/cut any pixels outside of that window from rendering...
As for buttons, we could do something similar for buttons rendering outside of the window, but since their interactive, and need to be clicked, we may need to think of a more clever solution (ie collapsable buttons, that shrink down to squares or a new dropdown if the window gets small enough... (note, I'm thinking specifically the buttons and dropdowns in the nav and subnav of widgets).
Describe alternatives you've considered
Haven't thought of many...
Additional context
I'd say this feature/bug is medium/high difficulty with medium/low priority, thus lets keep it on the back-burner for now?
Let's make it so graphics from 1 widget don't bleed out of the bounding box of their widget container!
Often times, the circular vizualizers in the EMG Widget and others will expand out and render over other widgets / graphics.. Buttons also do this to each other somtimes.
Describe the solution you'd like
This isn't an easy problem, but figuring out how to make it so all widget rendering functions are aware of their own rendering limitations, and then snip/crop/cut any pixels outside of that window from rendering... As for buttons, we could do something similar for buttons rendering outside of the window, but since their interactive, and need to be clicked, we may need to think of a more clever solution (ie collapsable buttons, that shrink down to squares or a new dropdown if the window gets small enough... (note, I'm thinking specifically the buttons and dropdowns in the nav and subnav of widgets).
Describe alternatives you've considered
Haven't thought of many...
Additional context
I'd say this feature/bug is medium/high difficulty with medium/low priority, thus lets keep it on the back-burner for now?