Node Visibility Issue

[gluon-bot]

Originally reported by: Akki Mahajan (Bitbucket: androizer, GitHub: androizer)

---

I've been using Gluon SB from past three months. Its faster than Oracle's deprecated SB. But from past few days, I've started encountering problems in it like:

1. Custom controls load exception while opening SB from IDE itself (read a workaround over here).
2. Sometimes, left click on every node/control on FXML gets disabled. Both on hierarchy and as well as live scene. (restart is not guaranteed to fix it. Mayb system restart, but not sure tho.)

And now this strange bug is freaking me out. Some of the portion of the nodes are not visible. I made them via SB, do some operations on them. I'll work fine for some days, and after that, nodes start getting invisible. Although the Visible property from SB always selected. Still nodes are not visible. And its not like its only the bug for custom controls, the stock Panes like Anchor, Split r mostly affected. On top of that, any control or shape on top of these Panes are also invisible.

Don't know exactly how to reproduce this issue for others, but its very hard to work with Scenes which r not usable. Sorry if this issue already exist, but I've searched thoroughly and couldn't find any existing.

---

• Bitbucket: https://bitbucket.org/gluon-oss/scenebuilder/issue/72

[gluon-bot]

Original comment by Jose Pereda (Bitbucket: JPereda, GitHub: JPereda):

---

Issue #1 is now fixed with Scene Builder 8.2.0.

As for #2 or #3, please try to attach an fxml that we can use to reproduce them, otherwise it's not possible to track them.

[gluon-bot]

Original comment by Akki Mahajan (Bitbucket: androizer, GitHub: androizer):

---

@jpereda, Thanks for the reply.
I've tested the latest build, but #1 issue is still persisting. Still getting FXMLLoad & CNF Exception.
and this is the FXML file for reproducing bug on your side.

[gluon-bot]

Original comment by Jose Pereda (Bitbucket: JPereda, GitHub: JPereda):

---

The issue is clear now: every component that you translate to negative coordinates won't be visible.
I've just moved them to 0 or positive coordinates, and all of them can be seen now.

As a suggestion: your FXML file is way too complex. You should try to split it in smaller FXML files, and use the Include menu. Then you will be able to work more easily on each of them.

[gluon-bot]

Original comment by Akki Mahajan (Bitbucket: androizer, GitHub: androizer):

---

This is what I actually thought, but if we use Oracle's Scene Builder 2.0, the node visibility varies which is totally weird.
As for the suggestion, em very thankful for it, but can u tell me how to add include menu? Any other source or blog? I'm kind of not much experienced in Scene Builder.
Edit: I kind of got the idea of this type of fxml is from this video.
https://youtu.be/5GsdaZWDcdY

[gluon-bot]

Original comment by Jose Pereda (Bitbucket: JPereda, GitHub: JPereda):

---

You can include an FXML file into another by using the fx:include tag, or in Scene Builder, with the option File->Include->FXML...

[gluon-bot]

Original comment by Akki Mahajan (Bitbucket: androizer, GitHub: androizer):

---

Oh. I see. Thanks for the prompt reply. Have u tried to inspect the fxml with the Oracle's SB 2.0?
And I just remembered that this bug is not old, it just came after a while when I was working on this project. Before that, my nodes were translated to -ve values and they were still visible. The case was using SB 8.1.1. I was having no issue with it, and after some weeks of working, the issue arrived.