JDK-4236146 : Frame and dialog refresh problems on Windows NT
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 1.2.2
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 1999-05-06
  • Updated: 1999-07-01
  • Resolved: 1999-07-01
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.3.0 kestrelFixed
Related Reports
Relates :  
Description
As a JFrame/JDialog is moved around over another JFrame on Windows NT,
parts of the frame/dialog are left in their old locations on the screen.
To recreate these refresh problems, execute the JCK Swing interactive 
tests for JFrame and JDialog on Windows NT.
Moving the frame/dialog under test over the test frame should recreate
the problem.

The tests that need to be executed for bug recreation are:
api/javax_swing/interactive/JFrameTests.html#JFrame
api/javax_swing/interactive/JDialogTests.html#JDialog


Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: kestrel FIXED IN: kestrel INTEGRATED IN: kestrel
14-06-2004

EVALUATION This is an awt bug, not sure of the bug number for it though so reassigning to awt. scott.violet@eng 1999-05-07 Sounds like the clip region corruption problem - 4045781 eric.hawkes@eng 1999-05-21 ----------- --------------- 6/24/99 kevin.ryan@eng -- On a PPro 200 with 64Mb and NT 4 SP 4, many "remnants" show up (i.e. title bars, frame edges) in underlying windows as you move the top frame around the screen. Performance on this class of machine is nowhere near acceptable. On a PII/400 with 128Mb of RAM and NT 4 SP 4, the repaint delays are still very noticeable, though no frame remnants (i.e., remnants of the actual native window frames) show up. [Tested by using multiple instances of the applet from bug # 4045781] ---- In AwtCanvas::WmEraseBackground we don't erase the backgroun when Windows wants us to, so during a window drag bits over window are left on the screen until the Java paint event comes around later and erases the background. We should erase immediately on WmEraseBackground (without calling up to Java code) so window portions are immediately erased. robi.khan@eng 1999-07-01
01-07-1999