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.
There is a problem in display of a textual diff. When a textual diff is selected as a diff visualizer, an empty window is opened. This problem was reported at nbusers: http://www.netbeans.org/servlets/ReadMsg?msgId=369981&listName=nbusers
This doesn't happen every time, and I don't know of a way to reliably reproduce it. I've seen it several times with the built-in CVS client on NetBeans 3.4 release.
I've seen it as well, once it starts appearing, the only workaround is to restart the IDE. happens to output of status, log, annotate as well.. maybe something with the way the mode is found and the TC shown??
Thanks Milos for your observations. So in this case we have two problems here: 1) diff window displayed using textual diff visualizer is empty This is perfectly reproducible and the cause of this is known. 2) output components (status, log, diff, ...) are *sometimes* blank. This has noting to do with diff, but probably with the mode and it's TCs. This is hardly reproducible. I'll fix 1) soon in dev builds, but 2) needs more investigation. Any hints and observations appreciated.
The first problem was fixed in diff/src/org/netbeans/modules/diff/builtin/visualizer/TextDiffEditorSupport.java 1.7. I've seen the second problem in Dan's test. It seems to me like a bug in window system. The TopComponent is completely gray including it's tab. I've looked into the code where the mode is created, but found nothing special, that could cause a bug like this. Therefore I'm moving this to core for evaluation. Can this have any association with issue #26842? The same mode is affected.
2 Martin: It always happens together with me: -----Diff Window [?]---------_[]X | | | Light Grey ;)) | | | ---------------------------------
Hi Max, thanks you for your observation. You're right. Sometimes it realy happend those 2 bug together issue #26842 issue #26811 but this one happens the very, very occasionaly and it realy doesn't have anything related too mentioned one. When "windows title it is broken" occures, it is possible to "reapair" itwithin the same ide session. But when you meet blank/gray windows you have restart the ide...
Unfortunately without way to reproduce I cannot find the reason why it happens. What GUI mode do you use? Is it specific to MDI or SDI?
Well we bouth(Martin and me) are using SDI (the not default one in current time) mode. The user who complained about it too, we don't know:-((
> The user who complained about it too, we don't know:-(( I have always used MDI.
> The user who complained about it too, we don't know:-(( I use MDI too, and what is strange - I have set up that all the windows reside in Main IDE's desktop - not separate windows, but when this bug occurs, the window is separate. Glenn, is it so with you?
I don't know how are those windows constructed, but if happens only for them, I expect the problem should be in those TopComponents. I don't know, just guess the diff, is constructed somehow from two CloneableEditors. If yes there needs to be called componentShowing on those CloneableEditors to initialize the editor pane, otherwise the component is just a blank panel. I expect there is the problem. Martin, please could you look at it?
NO, this is NOT the problem at all. This was a totally different issue, which happens only in text diff, not the graphical one. This was already fixed. If this would be the problem, the components would be blank *every time*. The blank windows appears also for status, log, etc. It's not a problem of diff. I assume, that there is either something bad with the Mode or the TopComponent or the Window System. I've looked at the Mode construction, I'll try to look at the TopComponents implementation also to see if there is anything that can cause this.
I've seen this in the editor several times lately as well. With multiple tabs open, sometimes going back to a tab that I had worked in previously shows the Grey Window of Death. Linux 2.4.18, Sun JDK 1.4.1 RC, NetBeans 3.4 in MDI mode.
I wonder if this can have any relation to issue #27109. There is described the problem with blank editor.
I believe, that this is not a problem in VCS modules. It has happened several times now in build 20021016-1447 when I was undocking Runtime tab to a new single frame. The undocked Runtime tab was blank. Please investigate the problem in core.
Please did you see this problem in latest dev builds?
I do not test much latest development builds and this bug appears rarely. But no, I haven't seen it since build 20021016-1447.
Neither I haven't seen this in latest dev builds.But I can't be so exact as Martin is;-)
I just found one case where component stay grey after IDE restart. It is issue #28273 - fix of #28273 could also solve this problem.
I haven't seen it anymore, another issue about not painted component , but obly on jdk1.3.1 is issue 31175.
Okay, verifying then. Thanks Marian for your judgement.
*** Issue 31522 has been marked as a duplicate of this issue. ***
I have the blank output windows for the CVS Output of the CVS diff command happening to me, most times it is reproducable. The Window Title would contain "CVS Output [?]". However, the contents of the window would be a solid grey box. I have a brand new installation of NB 3.4.1 on Win 2000 with JDK 1.4.1_02. My files that I were comparing were on a samba share on my Redhat Linux 7.3 box running samba 2.0.10-2. I mapped this samba share through Windows Explorer to my P: drive. I was comparing in the project tab showing in the Explorer(MDI GUI mode). I have CVS set up for GUI Style as well (I like the popup boxes). I have the CVS working directory root mounted (P:\catalog) as well as a relative mount point (P:\catalog\src). The relative mount point (P:\catalog\src) is the only mounted filesystem that is added to the project. I have reproduced this problem five times in a row following the steps listed below (with the config above): 1. Launch the NB IDE. 2. If the Project tab is not visible, switch to the project tab. 3. Expand the tree in the project tab. 4. Right click on the LMod file. 5. Select CVS -> Status from the context menu. 6. Click OK on the CVS Arguments for Status Window. 7. Click the View Diff button twice. (The first time I don't see the button activate [probably due to window focus issues], the second time it activates, but nothing happens.) 8. Close the CVS Output Window with the Window Title Bar close button (the little button with the X on it). 9. Right click on the same LMod file. 10. Select CVS -> Diff from the context menu. 11. Click OK on the CVS Arguments for Diff Window. Once the CVS Diff command doesn't work properly, it doesn't work for the entire IDE session. If I don't follow those steps exactly, there is a possibility that it will work porperly. Once it works properly, it works for the entire IDE session. I hope this is enough detail to have one of the developers that have looked into this issue to reproduce the problem.
Please is it reproducible on current dev build or at least on NB 3.5?
While it was perfectly reproducible on NB 3.4.1 under Windows 2000, jdk-1.4.1_01, SDI GUI mode, I can no longer reproduce this issue with NB 3.5rc2 under the same setup. But I also notice that instead of a separate window as in NB 3.4.1, the visual diff is now just another editor tab in NB 3.5rc2, a change I find of questionable usability, BTW.
Because Window System v1 will not be supported from now by our team, all old winsys issues (now "core/window system v1" issues) are going to be closed as WONTFIX. Changes in API which emerged both from UI spec and problems with adjusting to the older API are described in the document http://core.netbeans.org/windowsystem/changes.html. It shows also recommends how the client code should be adjusted to the new window system. If you think this issue apply also to the new winsys then change the subcomponent (to "core/window system") and REOPEN it.
issue doesn't apply to new window system - verified
This issue had *1 votes* before move to platform component