Closed 17cupsofcoffee closed 3 years ago
Fixed on the 0.6 branch. I have opted to move to a similar API to Raylib, with NineSlice
just being a config object rather than a wrapper around a specific texture. This is nice because it allows the same config to be used for multiple panels without holding onto any state. The config is also pretty lightweight (8 f32
s in total) so you could probably get away with defining it inline in draw
, if you wanted to.
Summary: NineSlice has a lot of issues:
I think it either needs improving, or deprecating.
Why is this needed? I'm currently reimplementing the same functionality as NineSlice in a game, because Tetra's version isn't good enough.