JavaFX TextField始终抛出“Empty String”错误问题咨询

Got it, let's figure out why your handlePrice() method is throwing that "Empty String" error when you try to type in the price TextField. This is a super common issue when dealing with numeric input in JavaFX, so let's break it down and fix it.

Why the Error Happens #

Chances are your current handlePrice() code is trying to parse the TextField's text directly into a number without checking if the string is empty first. For example, if you have something like this:

@FXML
private void handlePrice() {
    String priceStr = priceText.getText();
    // This line will throw NumberFormatException when priceStr is empty
    double price = Double.parseDouble(priceStr);
    // Rest of your logic...
}

When you start typing (before entering any characters) or delete all existing text, priceStr becomes an empty string. Double.parseDouble("") throws a NumberFormatException, which your code is probably catching and displaying as an "Empty String" error—blocking further input.

Solution 1: Add Null/Empty Checks + Exception Handling #

First, modify your handlePrice() method to handle empty strings and invalid input gracefully:

@FXML
private void handlePrice() {
    String priceStr = priceText.getText().trim(); // Trim whitespace to catch "   " as empty
    
    // Handle empty input first
    if (priceStr.isEmpty()) {
        // Optional: Set a default value or show a gentle hint (don't throw an error!)
        // Example: priceLabel.setText("Please enter a valid price");
        return; // Exit early so we don't try parsing an empty string
    }
    
    // Catch invalid numeric input
    try {
        double price = Double.parseDouble(priceStr);
        // Optional: Validate the price is positive (since prices can't be negative)
        if (price < 0) {
            // Show error: "Price can't be negative"
            return;
        }
        // Proceed with your logic (add to PartList, etc.)
    } catch (NumberFormatException e) {
        // Handle cases where input isn't a valid number (e.g., "abc", "12.34.56")
        // Example: priceLabel.setText("Please enter a valid number");
    }
}

Solution 2: Use TextFormatter to Restrict Input (Better Approach) #

To prevent invalid input from ever reaching your handlePrice() method, use JavaFX's TextFormatter to filter out non-numeric characters. This is cleaner because it stops bad input at the source.

Add this to your controller's initialize() method (make sure your controller implements Initializable):

@Override
public void initialize(URL url, ResourceBundle rb) {
    // Create a filter that only allows digits and one decimal point
    UnaryOperator<TextFormatter.Change> priceFilter = change -> {
        String newText = change.getControlNewText();
        // Regex allows empty string, digits, and optional single decimal point
        if (newText.matches("\\d*\\.?\\d*")) {
            return change; // Allow the input
        }
        return null; // Reject invalid input
    };
    
    // Attach the formatter to your price TextField
    priceText.setTextFormatter(new TextFormatter<>(priceFilter));
}

Now your TextField will only let users type numbers and one decimal point. Then you can simplify your handlePrice() method since you know the input is valid (or empty):

@FXML
private void handlePrice() {
    String priceStr = priceText.getText().trim();
    double price = priceStr.isEmpty() ? 0.0 : Double.parseDouble(priceStr);
    // Proceed with adding to PartList...
}

Bonus: Use a Listener for Real-Time Updates #

If you want to process the price as the user types (instead of on a button click), attach a listener to the TextField's textProperty() instead of using a separate handlePrice() method:

@Override
public void initialize(URL url, ResourceBundle rb) {
    // Add the TextFormatter from Solution 2 first...
    
    priceText.textProperty().addListener((observable, oldValue, newValue) -> {
        String trimmedValue = newValue.trim();
        if (trimmedValue.isEmpty()) {
            // Handle empty state (e.g., reset price to 0)
            return;
        }
        try {
            double price = Double.parseDouble(trimmedValue);
            // Update your model or UI in real-time
        } catch (NumberFormatException e) {
            // This should rarely happen thanks to the TextFormatter, but just in case
            priceText.setText(oldValue); // Revert to last valid input
        }
    });
}

The key takeaway is to never assume the TextField's text is a valid number—always handle empty strings and invalid input before trying to parse. Using TextFormatter is the most robust way to prevent bad input entirely.

内容的提问来源于stack exchange，提问作者nimbus_b