🚀 go-pugleaf

When a Java app calls repaint() after JOptionPane.show***Dialog(),
the repaint() is ignored because closing the dlg triggers a repaint() from
the system, and the Java "drawing system" skips the 1st request (from the
Java app) and executes only the 2nd (from the system).

This leaves some region unmodified in a panel (to which repaint() is
triggered)
because the repaint() from the system repaints only 'dirty' region (ie
region
covered  by the dlg). Here is a situation:

1)call repaint() to draw into a JPanel, jpnl, ie in jpnl.paintComponent(),
    g.draw***() are called.
2)call JOptionPane.show***Dialog() which is covering jpnl.
3)close the dlg, triggering jpnl.repaint() by the system
4)set some change (according to the inputs in the dlg) into effects in jpnl
   when drawn (such as new lines added)
5)call jpnl.repaint() to see the change.

Result is that 5) is not executed by the "drawing system" because of the
same call, jpnl.repaint(), in 3).

How can we force the "drawing system" not to skip consecutive repaint()
calls?
Or am I missing something?

Your suggestion or asnwer is greatly appreciated.