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
Set a different NegativeHeight, not just mostNegativeValue and negativeSections both which limits your data visualization, but with a height that sets a little bit different proportion (which is not a problem in my case) making it look a bit better and giving it a bit more flexibility for design? When I use negativeSections or mostNegativeValue if the data exceeds the section or value, which is symmetric to the positive value, it just disssappears. It would be great if every data would stay within its borderlimits and ideally percentage wise, doesn't go out of bound.
(sorry, the mobile app of Github mesed up my initial entry)
The text was updated successfully, but these errors were encountered:
freudarian
changed the title
Set a different NegativeHeight, not just mostNegativeValue and negativeSections both which limits your data visualization, but with a height that sets a little bit different proportion (which is not a problem in my case) making it look a bit better and giving it a bit more flexibility for design?
When I use negativeSections or mostNegativeValue if the data exceeds the section or value, which is symmetric to the positive value, it just disssappears.
It would be great if every data would stay within its borderlimits and ideally percentage wise, doesn't go out of bound.
Set NegativeHeight
May 20, 2024
Set a different NegativeHeight, not just mostNegativeValue and negativeSections both which limits your data visualization, but with a height that sets a little bit different proportion (which is not a problem in my case) making it look a bit better and giving it a bit more flexibility for design? When I use negativeSections or mostNegativeValue if the data exceeds the section or value, which is symmetric to the positive value, it just disssappears. It would be great if every data would stay within its borderlimits and ideally percentage wise, doesn't go out of bound.
(sorry, the mobile app of Github mesed up my initial entry)
The text was updated successfully, but these errors were encountered: