Support for floating-point component bounds?

It’s a change that we’d all love to make, but it’s also one where it’d be very hard not to make it break everyone’s code!

There are workarounds though - you can give your object a floating point position relative to its parent and then update the component bounds to be big enough to enclose it. Then in its paint method you just subtract the integer component position from the floating point target position and it looks correct. That’s how things like Drawables are done.

1 Like