Items added to a control like ListView, TableView, TreeView, are of an arbitrary type and are rendered via a CellFactory, not added as Nodes. (And in fact, as recent clarifications to the Javadoc mention, Nodes as items in the lists are strongly discouraged.). The items of a SplitPane are
One thing you could try still, whether acceptable or not, is to call
`applyCss` on the border pane before calling the count function.
As for the "and any children", I'm not sure how you should interpret
that. For a SplitPane, the nodes that are part of it are in the items
list (you don't add
That’s interesting. It leads me to wonder what is the expected result from a
call to lookupAll in various scenarios. If, after the window was showing, the
SplitPane divider is pushed all the way to one size such that the skin can
potentially choose to leave the hidden child out of the scene
Hi,
In this case, this is because SplitPane doesn't actually add its split
items as children -- only its Skin does this. Skins are AFAIK installed
after a CSS pass.
In the split pane case, I guess a Skin could choose to completely leave
out a child if its splitter completely hides it (ie,
I just want to make sure this is not expected behaviour. I don’t think so, the
documentation for lookupAll doesn’t mention anything related, but maybe I
missed something somewhere else.
I was just coding something to query the Scene for all SplitPanes and
save/restore the divider positions for
