This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
After unlocking your workstation, the NetBeans windows are not repainted until you click in them. Editor window requires a minimize/maximize cycle. Machine info: Windows XP SP1, NVIDIA GeForce4 Ti4600, J2SDK 5.0 beta 2 Other Swing apps do not display this behavior under J2SDK 5.0b2 also.
Evaluation: I was able to reproduce *sometimes* only with jdk 1.5 beta, with jdk 1.4.2 everything works OK. It's hard to say where the bug actually is, Tim could it be related to your redraw optimizations? I guess no.
Further clarification: Error I saw on my machine was that after workstation unlock, ontent of previously active window wasn't painted and I had to resize window manually to trigger correct redraw.
Sounds like a bug in 1.5 - we don't do anything terribly exciting that could cause it.
I just reproduced this error with SwingSet2 demo in JDK 1.5, so it's clearly JDKs issue. However, I can't reproduce the bug frequently, it happenned to me just two times, and it looks like error is dependent on timing of some sort. It's shame but it has no sense to file jdk issue when I'm not able to reproduce. Anyway nothing can be done on Netbeans side, so closing as wontfix.
closed
Users on the Sun Developer Network (aka Java Developer Connection) have added these comments: 2005-01-04 joegood This bug should be opened as a JRE 1.5 bug. I and I am sure others are experiencing this problem after locking and unlocking our WindowsXP computers. It is hard to re-create but it can be re-created with a little patience. It is unacceptable not to fix this bug. 2005-05-03 sesuler This bug needs to be opened back up. It makes our swing app look terrible. 2005-06-27 svetica This is reproducable with the JRE 1.5 if you have a JDesktop Pane with at least 1 active JInternal Frame as part of the UI.
artibee, if you have strong opinion about it feel free to reopen, I agree with David - it is very probably JDK issue. Dafe, is it possible to workarround this issue on our side ?
I see this bug daily on my home machine running windows XP - 100% reproducible - if I was running NetBeans, maximized, and the machine has been inactive for long enough that it goes to the login screen, when I log back in, the main window is completely gray and the only way to get it to fully repaint is to double click the titlebar to unmaximize and remaximize it. Steps to reproduce: Be running WinXP, no screen saver, no password on user account (note this machine is pre-Windows Service Pack 2, if that makes a difference) Start NetBeans Maximize the main window Leave the machine alone for 20 minutes or so. I wonder if either having a password dialog come up while logging back in, or running a screen saver, or not having NB maximized could make the bug harder to reproduce. No idea if there's anything we *can* detect on the NetBeans side to figure out that the repaint is needed - there may simply be no way for NB to detect that the repaint is needed, if no events are fired. Since I can reproduce the problem 100% of the time, I'll try reproducing this with a simple Swing app.
Tim, thanks for investigation. If you won't find anythign we can do , or you'll be sure it's JDK issue we can close it with appropriate statement. For now, I reopen it ... just to don't forget it ;)
So naturally, today I try to reproduce it and can't. It was 100% reproducible before I rebooted :-/ FWIW, I did find out that there should be a COMPONENT_RESIZED event on logging back in after the screen was locked...
I'm sorry but I can't do anything: 1) It *is* JDK issue for sure, I reproduced it randomly on Swing demo (see above) 2) I can't submit JDK bug, because I don't have reproductible test case, so it would be just wasting their time 3) No reasonable workaround I can think of.