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.
In recent dev builds, oftentimes the Projects window shows a blank gray area at the top, above any project root node that might be open. Not sure if reproducible, and can go away with a simple window refresh. I am guessing this is related to recent asynchronous Nodes changes.
Created attachment 66530 [details] Screenshot (JDK 6, Ubuntu, Ocean L&F)
Sorry, wrong component.
Can still be observed sometimes, e.g. in 080919.
I've seen this too in Metal L&F. I have no clue what it is caused by.
*** Bug 154522 has been marked as a duplicate of this bug. ***
*** Bug 187891 has been marked as a duplicate of this bug. ***
Bug 154522 documents a case where the gray bar appears at the top of the Files window. I've seen the gray bar in the Editor window too, below the editor tabs and Editor Toolbar but above the editor itself. I've also seen it in the Projects window, as the original reporter did. Both instances were in 6.9 (Build 201006101454).
Please disregard the reported instance of this showing up in editor bar. The gray bar I saw in the editor was the one which displays the tag hierarchy of the cursor position in an HTML document. At the time, the cursor was outside any tags, so the bar was blank.
Happens to me pretty regularly, so if some diagnostic can be applied I would be happy to know what it is.
I have unassigned myself from the bug as a signal that I don't know have expertise to find out what is wrong, someone who understands Swing has to look at the problem. Don't assign the bug to me, it is useless, I am not going to do anything with it.
I recently saw this happen when switching Project groups. I assume that triggers a redraw.
*** Bug 191797 has been marked as a duplicate of this bug. ***
Just observed at top of Maven Repositories window, so not likely anything specifically about the Projects window; perhaps some issue with BeanTreeView.
Created attachment 112430 [details] Project that exhibits the error. See video for how to reproduce with attached project. Video: http://www.youtube.com/watch?v=msSJ0HAryRI
Product Version: NetBeans IDE Dev (Build 201110240600) Java: 1.7.0_01; Java HotSpot(TM) Client VM 21.1-b02 System: Windows Vista version 6.0 running on x86; Cp1252; en_US (nb)
*** This bug has been marked as a duplicate of bug 197514 ***
Were you able to reproduce according to instructions from comment #14 and confirm that 07e9d09018bf fixes it? And if so, any clue why getPathBounds would be returning a rectangle with a negative height? (This sounds like a Swing bug.)
(In reply to comment #17) > Were you able to reproduce according to instructions from comment #14 and > confirm that 07e9d09018bf fixes it? And if so, any clue why getPathBounds would > be returning a rectangle with a negative height? (This sounds like a Swing > bug.) yes, i did reproduce it i'm just guessing but it might have been root node which is set not to show in the tree.
This does not seem to be fixed. Happened to me in 20111209-74a6d3d1f6af on 7u1 on Linux, Ocean L&F. Projects tab showed a one-row gray space above the root node for the one open project. As in bug #197514 comment #5, docking Files into its own mode fixed the rendering of Projects as a side effect.
Happening frequently in my usual userdir, and has been observed in GTK L&F on 6u30 in a test userdir.
Try to generate AWT component hierarchy dump (Ctrl-Shift-F1). Hopefully it explains something.
Just happened to me when opening a project group. (dev build, 7u2, Oneiric). Here is something of interest: I pressed Page Down, moving the selection from the first project in the group to the last, and suddenly the blank area disappeared (with the project nodes moving up one row). Will attach hierarchy dumps.
Created attachment 114236 [details] Hierarchy dump while problem was visible
Created attachment 114237 [details] Hierarchy dump after problem corrected by Page Down Diffing to the previous dump, there are a few relevant changes (i.e. those inside ProjectTab.ProjectTreeView): 1. lastPaintPosition for ProjectTreeView and its JViewport changed from (0,18) to (0,0). 2. The y-position of the TreeView.ExplorerTree changed from 18 to 0. 3. An HtmlRendererImpl inside the CellRendererPane inside the ExplorerTree vanished.
Created attachment 114323 [details] What has changed when the problem corrected itself There were some changes in notifications UI, but they are likely unrelated. However the wrong AWT hierarchy snapshot contains "HtmlRendererImpl" which is missing in corrected snapshot. TreeView$ExplorerTree is at position 18 on the wrong snapshot (explains why there is a gray area) - I am not sure if this can be related to present/missing HtmlRendererImpl class. Swing related issue. Stando, do you have any comments?
Yes, my guess was that the HtmlRendererImpl has a height of 18 pixels and is causing the problem; but I am unsure how this got added as a child. Maybe it is being added and then removed to set parent properties correctly for rendering, but the remove occasionally fails and so it does not get cleaned up? I tried to look through the cell rendering code in Swing but got lost.
my guess is that the blank bar is caused by JTree.scrollRectToVisible() call with negative y value. pressing page down key changes the selection which means another scrollRectToVisible() call with corrected coordinates. jesse, can you reproduce this?
(In reply to comment #27) > pressing page down key changes the selection But note that changing the selection in other ways - e.g. Down arrow key - does not correct it. Just Page Down. > can you reproduce this? No, but it happens frequently.
(In reply to comment #28) > (In reply to comment #27) > > pressing page down key changes the selection > > But note that changing the selection in other ways - e.g. Down arrow key - does > not correct it. Just Page Down. > > > can you reproduce this? > > No, but it happens frequently. i can try overriding scrollRectToVisible in TreeView to refuse scrolling to negative coords. would you be willing to test the patch to see if the makes any difference?
Well I have no way of knowing how long I would have to wait to see this happen, and I would rather not run patched builds indefinitely. If you believe negative coords are the problem, and these ought to be invalid, then try just adding an assertion. If it never gets reported, then something else was the problem. If it does get reported in some dev build, you have confirmed your hypothesis and may be able to fix the bug.
actually it seems that Jarda reintroduced this problem in #200865 so i've corrected his fix in core-main c49b31f59436. let's see if it helps
Integrated into 'main-golden' Changeset: http://hg.netbeans.org/main-golden/rev/c49b31f59436 User: S. Aubrecht <saubrecht@netbeans.org> Log: #142850 - Blank gray bar sometimes displayed at top of Projects window (fixing patch for #200865)