On Tue, 20 Oct 2026 17:03:50 GMT, Marius Hanl <[email protected]> wrote:
> This is basically a general problem for any program that allows arbitrary > callbacks (which in JavaFX are often hidden in events/listeners). Calling any > callback while you're structure isn't in a fully consistent state is > problematic if your code must continue working no matter what If I understand this correctly, this is not a problem per se, as long as the process converges and has no loops. In other words, a single property change might trigger a cascade of updates which must eventually settle. Once settled, the `layoutChildren()` does the layout and updates the scene graph. Perhaps what we need is to detect the loops? Or am I missing something? -- Another, related, scenario is when the update cascade requires explicit layout pass (or N passes, as it happened in RichTextArea with N=2). It is possible to let the multiple pulses do their job, at the risk of flicker or perpetual layout going on (I've seen that). I think it is better to explicitly acknowledge these cases and design for them. ------------- PR Review Comment: https://git.openjdk.org/jfx/pull/2347#discussion_r4328626120
