You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@netbeans.apache.org by "Anthony Romano (Jira)" <ji...@apache.org> on 2020/08/21 13:21:00 UTC
[jira] [Updated] (NETBEANS-4724) Missing New File Category JavaFX
[ https://issues.apache.org/jira/browse/NETBEANS-4724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anthony Romano updated NETBEANS-4724:
-------------------------------------
Description:
This is an intermittent bug that occasionally occurs right after an "FXML JavaFX Maven Archetype (Gluon)" project is created. Once, the user tries to create a New File for the project, the JavaFx option in the category list will not be present. One of the prominent contributors on the Netbeans mailing list surmises that the issue might be related to the ergonomics. Apparently the ergonomics automagically disable modules, not in use, however, it is supposed to automagically enable modules when needed and intermittently fail to do it.
This intermittent bug has a terrible side effect on the FXML file that is created after the JavaFX is reactivated. If the user right-clicks on the FXML file, the standard dropdown menu does not provide the option of "Make Controller", which means, if the user updates the content of the FXML the new changes would not manifest in the controller code unless the user manually keeps the FXML in sync with the controller (an error-prone process). The other side-effect is the “Open” menu option from the dropdown no longer invokes the Scene-Builder (if the Scene-Builder installed and set up with the Netbeans).
was:This is an intermittent bug that occasionally occurs right after an "FXML JavaFX Maven Archetype (Gluon)" project is created. Once, the user tries to create a New File for the project, the JavaFx option in the category list will not be present. One of the prominent contributors on the Netbeans mailing list surmises that the issue might be related to the ergonomics. Apparently the ergonomics automagically disable modules, not in use, however, it is supposed to automagically enable modules when needed and intermittently fail to do it.
> Missing New File Category JavaFX
> --------------------------------
>
> Key: NETBEANS-4724
> URL: https://issues.apache.org/jira/browse/NETBEANS-4724
> Project: NetBeans
> Issue Type: Bug
> Affects Versions: 12.0
> Environment: Windows 10, Netbeans 12.0
> Reporter: Anthony Romano
> Priority: Major
>
> This is an intermittent bug that occasionally occurs right after an "FXML JavaFX Maven Archetype (Gluon)" project is created. Once, the user tries to create a New File for the project, the JavaFx option in the category list will not be present. One of the prominent contributors on the Netbeans mailing list surmises that the issue might be related to the ergonomics. Apparently the ergonomics automagically disable modules, not in use, however, it is supposed to automagically enable modules when needed and intermittently fail to do it.
> This intermittent bug has a terrible side effect on the FXML file that is created after the JavaFX is reactivated. If the user right-clicks on the FXML file, the standard dropdown menu does not provide the option of "Make Controller", which means, if the user updates the content of the FXML the new changes would not manifest in the controller code unless the user manually keeps the FXML in sync with the controller (an error-prone process). The other side-effect is the “Open” menu option from the dropdown no longer invokes the Scene-Builder (if the Scene-Builder installed and set up with the Netbeans).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@netbeans.apache.org
For additional commands, e-mail: commits-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists