EDT NullRepaintMgr & setIgnoreRepaint

There have been a few discussions about Brackeen’s NullRepaintMgr in this forum.

Does anyone know if installation of this NullRepaintMgr (via the EDT) eliminates the need to set Component.setIgnoreRepaint(true) for each Swing component?

Said another way, if one wants to eliminate OS-originated repaint calls, it would appear that setIgnoreRepaint must be called for EACH Swing component used (every panel, button, etc…). Some GUIs have ALOT of components! If one uses NRM above, does it intercept the OS repaint calls in addition to the EDT-originated repaint calls? - ie. does the OS call the EDT repaint manager to get it’s repaint done?

Thanks,

Surely setIgnoreRepaint on the top-level Container Window will propagate to all of the Components it contains?

That is what I thought too, so I looked for a statement to that effect without finding such, and then tested the
concept. Unless I did the experiment incorrectly, my tests showed me it didn’t propogate to children. Also, the reading
I’ve done always says 'you must set the componentS - always in plural.

Any additional thoughts?

what do you you want to do with this command?

I’m quite sure that you need just setIgnoreRepaint(true) on top level container.
And no, you still need to install NullRepaintManager, as this only ignores repaints from OS, not AWT inside application itself.
Why do you need it anyway, are you trying active rendering with swing? If so, you couldn’t have missed this thread, it’s still high on first page, you can find example how to use nullrepaintmanager.