自定义LookAndFeel中JTextField在JTabbedPane切换时绘制异常排查

Hey there! Let's dig into this JTabbedPane + custom JTextFieldUI issue you're hitting. This is a classic gotcha with Swing's UI delegation and component rendering, so let's break down the most likely root causes and how to fix them:

1. Shared UI Instance (Most Probable Culprit) #

Swing’s UI delegation model can reuse UI instances across components if you don’t enforce one instance per component. If your custom JTextFieldUI is a singleton or gets reused across text fields (even across tabs), state from one field will leak to others when tabs switch.

How to Check & Fix: #

Look at your createUI method in the custom UI class. If you’re returning a static instance, that’s the problem:

// ❌ Wrong - singleton UI causes cross-component state leaks
private static final MyTextFieldUI INSTANCE = new MyTextFieldUI();
public static ComponentUI createUI(JComponent c) {
    return INSTANCE;
}

// ✅ Correct - each component gets its own fresh UI instance
public static ComponentUI createUI(JComponent c) {
    return new MyTextFieldUI();
}

2. Unreset Painting State in UI Delegate #

If your custom UI stores component-specific state (like cached colors, bounds, or graphics objects) as instance variables without resetting them, that state will persist when the UI repaints a different component (e.g., a text field in another tab).

How to Check & Fix: #

• Always reset component-specific state in installUI(JComponent c) before painting.
• Never rely on leftover state from previous paint calls. For example, if you cache a background color, refresh it using the current component’s properties every time you paint:

@Override
public void paint(Graphics g, JComponent c) {
    JTextField field = (JTextField) c;
    // Reset state using the current component's properties
    Color bgColor = field.isEnabled() ? CUSTOM_ENABLED_BG : CUSTOM_DISABLED_BG;
    g.setColor(bgColor);
    g.fillRect(0, 0, field.getWidth(), field.getHeight());
    // Rest of your painting logic...
}

3. Missing Visibility Change Handling #

JTabbedPane toggles component visibility with setVisible(false)/true when switching tabs. If your custom UI doesn’t trigger a full repaint when a component becomes visible again, leftover rendering artifacts can stick around.

How to Fix: #

Override componentVisibilityChanged in your UI delegate to force a full repaint:

@Override
protected void componentVisibilityChanged(ComponentEvent e) {
    super.componentVisibilityChanged(e);
    e.getComponent().repaint(); // Force full repaint when component becomes visible
}

4. LookAndFeel UI Mapping Conflicts #

If you registered your custom UI via UIManager.put("TextFieldUI", "com.yourpackage.MyTextFieldUI"), some default LookAndFeels use instance pooling that can cause cross-tab leaks.

Quick Test: #

Explicitly set the UI on each text field instead of relying on the UIManager mapping:

JTextField tab1Field = new JTextField();
tab1Field.setUI(new MyTextFieldUI());

JTextField tab2Field = new JTextField();
tab2Field.setUI(new MyTextFieldUI());

If this fixes the issue, your LookAndFeel’s pooling is the problem.

Add a debug log in your UI’s paint method to confirm if the same UI instance is used across multiple components:

@Override
public void paint(Graphics g, JComponent c) {
    System.out.println("UI Instance: " + this.hashCode() + " painting Component: " + c.hashCode());
    // Rest of painting logic...
}

If you see the same UI hash code for text fields in different tabs, you’ve confirmed instance reuse is the issue.

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