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.

Bug 25982 - compiler status badge on the Editor's tab
Summary: compiler status badge on the Editor's tab
Status: VERIFIED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-24 15:32 UTC by andrew
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description andrew 2002-07-24 15:32:51 UTC 
It is for release34 branch about 10 hour ago 
(MDI, w2k, j2se 1.4.0_01, JavaCVS FS)

- open java object in the editor
- close objects's package in the Explorer
- edit the file
- compile

result: compiler status badge on the editor's tab is
still "uncompiled"

- open file's package in the Explorer

result: the badge became well (have disappeared)
Comment 1 Jan Becicka 2002-07-24 16:08:44 UTC 
Changing priority to P3. User data is not corrupted, no crash or
deadlock. Not a critical usability problem.
Comment 2 andrew 2002-07-25 08:55:51 UTC 
OK, formally it is indeed P3.

But the bug is very widely seen, so it is very annoying.
Every day every user every minute will see it,
and there will be $$$ millions NB 3.4 users :-)
I suggest to change Target Milestone to 3.4. Is it
possible at HR mode?
Comment 3 Jan Becicka 2002-07-25 10:21:10 UTC 
I'm afraid this bug will not be fixed for 3.4.
I cannot even reproduce it.
Andrew, badges are sometimes updated very lazy. It means after several
seconds. Is it your case? Try to wait for ~5 seconds. Are the badges
OK now? I admit, that 5 seconds are not acceptable. Compiler badges
are still the problem. See issue 23404, issue 13133, issue 11183.
Comment 4 andrew 2002-07-25 15:00:45 UTC 
iwno> I'm afraid this bug will not be fixed for 3.4.

It is very sad :-(

iwno> I cannot even reproduce it.

It is indeed is not 100% reproducable. But it takes place very
often for me (more than 50%).

iwno> Andrew, badges are sometimes updated very lazy. It means after several
iwno> seconds. Is it your case? Try to wait for ~5 seconds. Are the badges
iwno> OK now? I admit, that 5 seconds are not acceptable.

It may be as long as I don't touch the IDE, or don't open class's
package in the Explorer.

iwno> Compiler badges
iwno> are still the problem. See issue 23404, issue 13133, issue 11183.

IMPORTANT: this issue was born by _last_ commitings to release34
branch - not later then 20 hours before HR mode was turned on.
So, it is regression. May it be connected with issue 25531?
Comment 5 Jan Becicka 2002-07-25 16:06:34 UTC 
Sorry I cannot reproduce it.
1. I started build 200207242340 (release34) with clean userdir
2. I mounted CVS filesystem.
3. I opened .java file using File | Open File (not using Explorer)
4. I edited the file (badge appeared)
5. I compiled the file (badge disappeared)
Comment 6 Jan Becicka 2002-09-10 15:00:55 UTC 
Andrew, can you reproduce it in NB 3.4?
Comment 7 Tomas Hurka 2002-09-24 18:04:21 UTC 
Closing as works-for-me. Please, reopen if you can reproduce it with NB 3.4
Comment 8 andrew 2003-07-08 18:59:24 UTC 
VERIFIED