** Uups, looks like I've posted on the wrong forum! Needs to be in Swing / AWT / SWT **
Although that might seem to be a beginner's problem I'm having it in quite an unusual context.
I've got a JFrame (Swing component) all of whose children are AWT Components. Those Components (Canvas, in fact) are displaying buffered images that are concurrently updated by other threads. A java.util.Timer is repainting the frame at fixed rate. Although I see that the all the components are being painted over and over (a message is printed from one of the component's paint() method) the JFrame itself does not change visually until OS requests repainting (e.g. I change the size of the window).
All the Swing-related activities are performed from the AWT event dispatching
thread; JFrame is repainted using frame.repaint().
Unfortunatly I cannot provide the actual code here because it is linked to my entire project, so here is a simplified version:
Why do I only use Swing for the frame? Well, at first I wanted to make an AWT application (less useless (in my case) processing, amiright?) but it turned out I needed double bufferisation in order to reduce artifacts on screen updates.
Thanks in advance