3

Given an .fxml include like:

<fx:include fx:id="header" source="Header.fxml" />

The Java FXML docs say to create two variables like:

@FXML private HBox header;
@FXML private HeaderController headerController;

What determines the controller variable name? Is it always just the include id followed by "Controller"?

3
  • 1
    It's not explicitly stated in the documentation, but that is how I interpret it (and it always seems to work that way.) Commented Jun 10, 2017 at 0:00
  • What better way is there to identify which controller is associated with the fxml file? Commented Jun 10, 2017 at 4:56
  • @SedrickJefferson something like header.getController() and a variable name I can control? Commented Jun 12, 2017 at 15:26

1 Answer 1

5

Yes the field name the controller is injected to is always constructed by concatenating the fx:id of the <fx:include> tag with "Controller".

It's "hidden" in the documentation of the FXMLLoader.CONTROLLER_SUFFIX field.

A suffix for controllers of included fxml files. The full key is stored in namespace map.

(The namespace map contains all the objects by the field name they are injected to, if such a field exists.)

You can verify that it's value is "Controller" here: https://docs.oracle.com/javase/8/javafx/api/constant-values.html#javafx.fxml.FXMLLoader.CONTROLLER_SUFFIX

Sign up to request clarification or add additional context in comments.

1 Comment

Very comprehensive answer! Thank you.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.