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.
070718, but I think broken also in 070716? When an Ant process is running, normally the OW tab title is boldfaced. In these builds, the tab instead displays the raw HTML, e.g. "<html><b>...</b>".
Forgot to mention: running with -J-Dnb.tabnames.html=true
I don't think a P2 can be justified if it happens with a system property setup only.
True. Though I think we should consider making this mode the default since it's much nicer than little asterisks. Tim did the original impl, if I recall correctly, so he may have some tip on what is wrong?
Well, somebody's been doing something to the tab control - in today's build, all of the navigation controls are missing from the right side of the editor tab control.
The only thing -J-Dnb.tabnames.html=true should affect is how editor tab display names are computed. There's no code that I know of that would cause that line switch to affect the output window's title.
I assumed jesse means the output title that is normally bold when there is just one tab in OW and a build is running. jesse, are you using gtk l&f by any chance? (found this one in fisheye that could be possibly related: http://deadlock.netbeans.org/fisheye/changelog/netbeans?cs=MAIN:dsimonek:20070716145642)
I have multiple tabs in the OW. Normally the subtabs are boldfaced when a build is running. In recent builds they show as HTML instead. I am not using GTK. I am using Ocean L&F, on JDK 7 b15. If you have trouble reproducing, just let me know and I will spend some time trying to identify the trigger condition.
ok. then it's not related to nb.tabnames.html=true. can you try with jdk16? If I recall correctly all we do is rely on swing to handle html correctly in tab titles..
Of course I cannot reproduce in another userdir, even with the same build, JDK, LAF, and -D switch...
...nor even in the same userdir after a restart. I have also noticed something else funny in the past few days: the tab names in the OW suddenly change to the wrong value. In the screenshot I will attach, I first ran a CVS update operation on some file. This produced a tab named something like "CVS on cfg-unit.xml" or whatever. Then I built the core module. This produced a second tab "core (netbeans)", as expected. But just when the build finished, the title of the other tab switched to "core (netbeans)" as well!
Created attachment 45398 [details] Screenshot
Created attachment 45399 [details] Same IDE session, simply closed "real" core(netbeans) tab... note that OW window title now corrected
Originally reported bug still happens sometimes after the restart, but not most times. I cannot figure out how to reproduce. The tab title switch I can reproduce, just by alternately building core and updating that file.
Regarding title swap, I am currently in a mode where the OW shows (I will use asterisks to represent correctly rendered boldface): Output ----------------------------------------- core (netbeans) x | *core (netbeans)* x | ----------------------------------------- (The first is actual Ant output, the second is really CVS output.) If I build core, I first see Output ---------------------------------------------------- *core (netbeans)* x | :pserver:....../repository x | ---------------------------------------------------- and then back to the first appearance when the build completes.
Created attachment 45413 [details] Example of originally reported problem, finally
Created attachment 46235 [details] Log from 070806 + private logging patches, JDK 7 b17; ran one build (looked OK), did CVS diff, ran second build and saw both problems
Note also the tripling of ' ' in the HTML title shown in this log, which I cannot explain.
Tried running similar actions in my regular userdir under JDK 6 for a while and have yet to see the bug. So I suspect this is some kind of problem in JDK 7's JTabbedPane which needs to be filed.
I know JDK 6 switched to using JLabels (which you can replace) in tab titles; maybe that has something to do with it?
But I think it is specific to JDK 7, not 6.
Just figuring since the code's been messed with recently in JDK 6, it's probably been messed with some more in JDK 7. Richard Bair might be the person to talk to.
Reassigning to new module owner Tomas Holy.
Is this issue still relevant? Was it JDK bug?
I don't know, I have not been using JDK 7 for a while now (due to an unrelated serious AWT bug).
JDK 7 issue. *** This issue has been marked as a duplicate of 113388 ***
v/c