JTextField doesn't cause a validateTree()

Question

Hello,
I've written a new layout manager. If I change the visible state of a component the layout manager should do a new layout. This works for
JLabel, JButton, JRadioButton, JCombobox, JPanel and JCheckbox but not for JTextField.
After debugging I noticed, that JTextField is the only Component witch ovewrites the method isValidateRoot() and so it returns true instead of false. This causes that the RepaintManager.addInvalidComponent() returns before it adds an event to the EventQueue if the JTextfield is changed to visible = false.
Is this a bug, or how can I solv this problem?
Thx
Guido

Answer 1

If somebody has an answer to this question I would still be very interested.
I am also puzzled about the logic inside the method isValidateRoot() inside JTextField:
    public boolean isValidateRoot() {
     Component parent = getParent();
     if (parent instanceof JViewport) {
         return false;
        return true;
    }Meaning the JTextField is itself in charge for handling layout updates inside its own boundaries, but also when calling setVisible(true) on the JTextField. The documentation says that it is for handling calls to revalidate from within the component itself (unless it is contained inside a JViewport). I don't understand this. If anyone can explain this?
At first sight overriding isValidateRoot() always returning true in a subclass of JTextField would also solve the problem. But that could lead to a much heavier revalidation of the internal JTextField mechanisms?
Conclusion (without knowing answers to the questions above) is that when you call setVisible on a JTextField that you have to call revalidate() on its container again in order to see the new layout situation.