Node Z-Order question

Question

So I've been scouring the net for any clues as to how to get Z-Order working on the actual scene itself and not just within a node group.
I understand that's how toFront/toBack currently works as per the API documentation.
I found this bug: [#RT-2783|http://javafx-jira.kenai.com/browse/RT-2783?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel]
Now, from the comments, a single Richard Blair says this: Fixed in latest marina workspace. I actually have fixed the implementation so that it happily sorts the nodes in the Scene as well as in a Group, rather than changing the documentation to make permanent a bug in the implementation ;-).+
Then again, I'm not entirely sure what the "latest marina workspace" is.
Is this true? Can nodes now be sorted from within the scene.content sequence or do "workarounds" still need to be done (i.e. delete and re-insert node into scene.content -- which causes an "*An attempt has been made to add node to a new group without first removing it from its current group*" warning for me by the way).
I'm having issues with my menu system (naturally) as it's the first set of nodes on the scene graph, thus having the lowest z-order. Anyone else out there successfully implemented a menu system that correctly stays on top of any other nodes on the scene graph?
Cheers!
and Happy Holidays!

Answer 1

Not sure what could be going on. Could you post some simple example code that illustrates the problem?
Hmmm, here's a guess at what might be going on. Apologies if this is way off base.
The toFront() and toBack() functions only work to alter the stacking order of a node relative to its siblings, that is, other nodes that belong directly to the same group or scene. You can't use them to restack nodes relative to nodes in another Group. For example, consider this:
Scene {
    content: [
        g1 = Group { content: [a, b] },
        g2 = Group { content: [c, d] }
}If you call a.toFront(), it will move node a in front of node b, but not in front of nodes c or d. To move node a all the way to the front, you also have to call g1.toFront(). Of course, this also move node b in front of nodes c and d. Does this explain what might be going on?