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 55346 - OK button is randomly disabled in set main class dialog
Summary: OK button is randomly disabled in set main class dialog
Status: CLOSED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Project (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Tomas Zezula
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2005-02-22 13:14 UTC by Roman Strobl
Modified: 2006-03-24 13:07 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Project where it fails (10.46 KB, application/octet-stream)
2005-02-22 13:15 UTC, Roman Strobl
Details
Screenshot (132.41 KB, image/png)
2005-02-23 09:26 UTC, Roman Strobl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Strobl 2005-02-22 13:14:29 UTC
[NetBeans 200502211900; JDS R3; JDK 1.5.0_02]

When setting main class for attached project I am
sometimes not able to click on the OK button
because it is disabled. Sometimes the button is
disabled and sometimes not. I wasn't able to
reproduce it on another project, although there's
nothing special on the attached project IMO.
Comment 1 Roman Strobl 2005-02-22 13:15:32 UTC
Created attachment 20452 [details]
Project where it fails
Comment 2 Jan Chalupa 2005-02-22 19:52:39 UTC
Roman, you didn't try to set the main class with "background scanning"
turned on, did you?
Comment 3 Roman Strobl 2005-02-23 09:25:03 UTC
The bug is independent on the background scanning property setting.
Today it was harder for me to reproduce it (seems as some random race
condition to me...). Today it failed in 1 case of cca. 50 while
yesterday it failed in 1 case of cca. 5. I attach screenshot of the
dialog. A workaround is to close the dialog and try again, the
probability that OK button won't be disabled next time is high.
Comment 4 Roman Strobl 2005-02-23 09:26:23 UTC
Created attachment 20466 [details]
Screenshot
Comment 5 Tomas Zezula 2005-02-24 12:39:05 UTC
This is a threading issue, the listeners are registerd int the AWT
Thread after the async job searching all main classes is started and
the async job (non AWT Thread) calls back into AWT.
Comment 6 Tomas Zezula 2005-02-24 12:54:58 UTC
Checking in
src/org/netbeans/modules/java/j2seproject/ui/customizer/MainClassChooser.java;
/cvs/java/j2seproject/src/org/netbeans/modules/java/j2seproject/ui/customizer/MainClassChooser.java,v
 <--  MainClassChooser.java
new revision: 1.27; previous revision: 1.26
done
Comment 7 Roman Strobl 2005-03-11 15:22:56 UTC
Verified on 20050311-1239.