Hi Martin,
On 30.07.2014 17:39, Martin Sladecek wrote:
I assume you don't change child1 Nodes, so it should work.
I may add/insert such nodes but in that case I take the easy route and
simply rebuild the complete hbox.
Yeah, one problem with layouts is when you want to do some layout that
Richard,
since I need to get x and width of child1 (the one inside the hbox) I
have to use boundsInParent. According to the docs layoutBounds.x/y are
always zero for resizable nodes so it does not work here. As to the
question whether the parent might be size 0: the HBox is indeed size 0
Martin,
thanks a lot for this elaborate explanation :) Here's an image of what
I am talking about.
http://postimg.org/image/t9a6esc71/
child1 is one of the labels in a hbox, e.g. Query or Result
child2 is the blueish region. It needs to be positioned under one of
those labels. I am doing
Richard,
Is there a sequence diagram (or similar) where the layout process is described
in detail?
It’s hard to in text get a clear and precise view on how the layout process in
the Node hierarchy is happening.
The sequence diagram would be good to have as a constraint for building layout
I created some simple diagrams for this blog post:
https://blogs.oracle.com/jfxprg/entry/the_peculiarities_of_javafx_layout
-Martin
On 07/29/2014 03:15 PM, Mikael Grev wrote:
Richard,
Is there a sequence diagram (or similar) where the layout process is described
in detail?
It’s hard to in
The super.layoutChildren should size every child of the control (which
is VBox), but not child's children. The control must finish the layout
before children can do theirs. If you need to do layout on some child
before that, you can call .layout() on it. It will do it's layout using
it's
