I'm a little confused about the role of the repaint manager and UI delegate in painting Swing Components. It seems like they might do some of the same tasks. Which one handles a call that results in the painting or repainting of a Swing component? Does the UI dlegate recieve the call initially and pass the look and feel information to the repaint manager, or is it the other way around. I looked at the API's and read the article "Painting in AWT and Swing" but I'm still a little confused. Thanks for any help, Landon [ March 05, 2004: Message edited by: Landon Blake ]
RepaintManager handles the overall mechanics of repainting... how often it should be done, keeping track of "dirty" areas, etc. UI Delegates specify the look and feel of the specific component.
Write once, run anywhere, because there's nowhere to hide! - /. A.C.
Joined: Jul 03, 2001
RepaintManager exists for two purposes: to provide efficient revalidation and repainting. It intercepts all repaint() and revalidate() requests. This class also handles all double-buffering in Swing and maintains a single Image used for this purpose. This Image�s maximum size is, by default, the size of the screen. However, we can set its size manually using RepaintManager�s setDoubleBufferMaximumSize() method.
This is from the excellent book Swing by Robinson and Vorobiev. Read more here