Enhancement: Improve codeviewer example: No protrude splittable both side .

[MulticolorWorld]

In the "vertical splitter" example currently used in codeviewer, the left side does not protrude due to the minimum size specification, but the right side has no limit and will protrude outside the window.
I'd like to improve this, but I'm wondering if you have any good examples.

Sorry Im poor English end use machine translation sorry.

[MulticolorWorld]

If this is not appropriate here, I would be grateful if you could guide me to the right place.

[MulticolorWorld]

How to get parent size or splittable itself in composable function? If exist, coerceAtMost() is work it.

[igordmn]

You can look at this:
9e67cfc

But it is not finished. If we resize the main window then we will see a small lag (size of the panel will not be immediately changed)

[MulticolorWorld]

Getting size of composable itself to use onSizeChanged() and size-state is workaround? Allow to use it normally?

[igordmn]

Getting size of composable itself to use onSizeChanged() and size-state is workaround? Allow to use it normally?

Probably the lag when we resize the main window caused by onSizeChanged (because the panel will be resized only on the second frame).

Probably we need to constrain sizes of panels not inside onSizeChanged, but inside VerticalSplittable function

[MulticolorWorld]

Oh, sorry. Apart from this issue, I wanted to ask if this usage is normal. Probably because there are going to be many situations where you want to know the size of itself.

[igordmn]

I wanted to ask if this usage is normal

Probably in most cases we should use Layout or WithConstraints

Because we will know the size of the container immediately (in the current frame).

But in the case it is not important to know the size in the current frame, we can use onSizeChanged and size-state.