(J)Applet.start() not called by event thread - violating Swing's policy?
Alas, I still have issues with my applet's screen refreshes.
As I had to learn I had a few places where I violated Swing's single thread policy and updated GUI components from threads other than the AWT event thread.
But now I just detected, that also the (J)Applet's start()-method is NOT called by the event thread. That would mean, that all GUI initialization code that I have in that method also violates that single thread policy. Or ist the start() method an exception to that rule?
The problem that I am observing is, that I have a split-pane, where one split's content gets updated depending on selections in the other split. However, when I select something, the other split either remains unchanged (even though the corresponding listener gets called and updates the component - I verified that!) or - even stranger: it get's cleared (i.e. contains no content all all).
But only when I subsequently leave the panel with the mouse or when I pull the split-pane divider, the split suddenly get's painted. Why is that update delayed and the display not fully refreshed immediately?
Again: all those refreshes work perfectly when running as a java application. Only when running as an Applet I witness these weirdoes...
Message was edited by: mmo18