Originally reported by: A. Walter (Bitbucket: awalterwork, GitHub: Unknown)
In SceneBuilder 8.3.0, when using multiple fx:reference blocks to refer to objects defined in fx:define blocks, sometimes (see below) you
cannot see edits you make to the FXML (they don't show up in the FXML file view in the center)
cannot do a normal save (Ctrl+S doesn't seem to do anything and the Save item in the File menu is greyed out).
I say "sometimes", because I found some scenarios where everything works fine and some very similar scenarios where the weird behaviour described above occurs. I'm not sure what exactly causes the different behaviour, but it is reproducable.
Steps to reproduce
Open any of the attached files called NotWorking_.fxml in SceneBuilder.
Try to edit the text of the button that says "Change my Text!" (change the text, hit Enter). The FXML file view in the center is not updated.
Try to save with Ctrl+S (nothing happens) or via the File menu (not possible).
Use Save As... and choose the the file you are currently editing. This updates the file in the file system, but the FXML file view in the center of SB is not updated. You still cannot save normally.
Open any of the attached files called Working_.fxml in SceneBuilder.
Edit the text of the button that says "Change my Text!" (change the text, hit Enter). The FXML file view in the center is updated.
Save with Ctrl+S or via the File menu (enabled).
(Note that all fx:references are removed on save - this behaviour is wrong and documented in bug #121 .)
The scenarios that work and do not work are very similar - see some snippets:
Edits should always show up and normal saving should be possible when multiple fx:reference blocks are used, regardless of where exactly they are used.
(Also, the fx:references should not be deleted on save - see bug #121 ).
Originally reported by: A. Walter (Bitbucket: awalterwork, GitHub: Unknown)
In SceneBuilder 8.3.0, when using multiple fx:reference blocks to refer to objects defined in fx:define blocks, sometimes (see below) you
I say "sometimes", because I found some scenarios where everything works fine and some very similar scenarios where the weird behaviour described above occurs. I'm not sure what exactly causes the different behaviour, but it is reproducable.
Steps to reproduce
Open any of the attached files called NotWorking_.fxml in SceneBuilder.
Try to edit the text of the button that says "Change my Text!" (change the text, hit Enter). The FXML file view in the center is not updated.
Try to save with Ctrl+S (nothing happens) or via the File menu (not possible).
Use Save As... and choose the the file you are currently editing. This updates the file in the file system, but the FXML file view in the center of SB is not updated. You still cannot save normally.
Open any of the attached files called Working_.fxml in SceneBuilder.
Edit the text of the button that says "Change my Text!" (change the text, hit Enter). The FXML file view in the center is updated.
Save with Ctrl+S or via the File menu (enabled).
(Note that all fx:references are removed on save - this behaviour is wrong and documented in bug #121 .)
The scenarios that work and do not work are very similar - see some snippets:
NotWorking1.fxml
NotWorking2.fxml
NotWorking3.fxml
Working1.fxml (identical to NotWorking1.fxml except for button order in VBox)
Working2.fxml
Expected behaviour