On Thu, 27 Aug 2026 14:44:47 GMT, Marius Hanl <[email protected]> wrote:
>> We can't trust those, as they delegate to user overridable methods. Also, >> even if they did snapping there, which "isSnapToPixel" would they use? If >> they use their own, that would be useless for the parent as it may have a >> different setting. If they use their parent's snapToPixel, then you have to >> deal with there being no parent (yet). >> >> Possibly we could include the snapping logic in `Parent` itself (it caches >> the result of the compute methods). Those methods are final, so can't be >> changed. In that way, everyone would automatically adhere to the rules, and >> there would be no need to resnap these values when queried... hm.... > >> Possibly we could include the snapping logic in `Parent` itself (it caches >> the result of the compute methods) > > interesting idea, might be worth to explore. > I'd expect `snapSize` really, since the minimum width is the size of the > content. This is the available size, not a content allocation. For example, if the pane has an available size of 100.01, then we shouldn't snapSize this value and arrive at an available size of 101. ------------- PR Review Comment: https://git.openjdk.org/jfx/pull/2262#discussion_r3873913120
