JavaFX：fx：id校对

Question

Entering fx:id 's manually across controllers and FXML files and late binding are a potential source of errors, fragilising code robustness (my personal opinion). On the other hand, it offers flexibility.

Is there a way of proofing the binding and identifying errors before revealing them at runtime, or is this the "by design" workflow and you have to make do and just be careful while coding ?

edit :
I am using Eclipse with e(fx)clipse, and Gluon Scene Builder

Answer 1

As far as I know there is no real "proof" like the javac which would complain. JavaFx to too dynmaic for this. The best thing you can do is adding the controller to your FXML file like this

<?xml version="1.0" encoding="UTF-8"?>

<?import java.lang.*?>
<?import javafx.geometry.*?>
<?import javafx.scene.control.*?>
<?import javafx.scene.layout.*?>

<ScrollPane xmlns="http://javafx.com/javafx/8" 
    xmlns:fx="http://javafx.com/fxml/1" fx:controller="com.myapp.MyController">
    <content>
        ...
    </content>
</ScrollPane>

This then allows Eclipse or IntelliJ (thx @silifly) to show you warning about elements which have not been binded to you controller. Bu this will not tell if the injection which is performed by the FXMLLoader was successful. You then could check during the initialization phase if your element has been injected correctly.

import javafx.fxml.FXML;
import javafx.fxml.Initializable;

public class MyController implements Initializable {

    @FXML
    private Button btnLogin;

    @Override
    public void initialize(URL location, ResourceBundle resources) {
        assert btnLogin != null : "fx:id=\"btnLogin\" was not injected: check your FXML file 'MyView.fxml'.";
    }
}

Those are the two facilities which I know and use a lot to check if everything has been setup correctly.

Edit:

I just saw that you don't need to implement the interface anymore you can just write

@FXML
public void initialize() {
    ...
}