You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Without setting fx:controller="someController" in the .fxml file, the initialize method never called !
So what the utility of the @FXMLController annotation.
The text was updated successfully, but these errors were encountered:
This is true. This annotation includes (as you see in the code) at the moment only the @component annotation, to 'component scan' it as a Spring Bean. We "invented" this annotation to
a) have a bit of semantic
b) be safe in the future to add some fields there.
Feel free to implement a convention for 'auto detecting' a controller from a bean. (In fact we haven't done this, because we could not agree on whether this should be called XYZController or XYZPresenter) ;-)
mtbadi39
changed the title
initialize method never called without setting fx:controller in fxml
Initialize method never called without setting fx:controller in fxml
Apr 19, 2018
mtbadi39
changed the title
Initialize method never called without setting fx:controller in fxml
Initialize method never called without setting fx:controller in .fxml
Apr 19, 2018
Without setting
fx:controller="someController"
in the .fxml file, the initialize method never called !So what the utility of the
@FXMLController
annotation.The text was updated successfully, but these errors were encountered: