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 142989 - [65cat] Double-clicking on Find Driver Keeps Progress Bar Loadng
Summary: [65cat] Double-clicking on Find Driver Keeps Progress Bar Loadng
Status: RESOLVED FIXED
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Windows Vista
: P4 blocker (vote)
Assignee: David Vancouvering
URL:
Keywords:
Depends on:
Blocks: 152436
  Show dependency tree
 
Reported: 2008-08-06 01:27 UTC by sunbiz
Modified: 2009-06-17 13:20 UTC (History)
1 user (show)

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 sunbiz 2008-08-06 01:27:35 UTC 
[ BUILD # : 080806 ]
[ JDK VERSION : other ]

[Product Version: NetBeans IDE Dev (Build 080806)]
[Java: 1.6.0_10-beta; Java HotSpot(TM) Client VM 11.0-b12]
[System: Windows Vista version 6.0 running on x86; Cp1252; en_IN
(nb)]

The progress bar that appears when finding a driver in the customize

section of a database driver continues to run forever. This happens 
if by mistake someone double clicks on the find button beside the 
driver name.

To reproduce the bug:
1.) Open Services Tab, Under Drivers, Right-click on any driver and 
click customize
2.) Suppose we clicked on MySQL Driver, you will see 
com.mysql.jdbc.Driver
3.) Click the Find button twice in quick succession.
4.) This makes the progress bar go on forever trying to search the 
driver.
Comment 1 David Vancouvering 2008-08-15 20:39:42 UTC 
We have a lot of bugs to fix and this one seems minor.  Do you agree or is this a constant annoyance?
Comment 2 sunbiz 2008-08-15 20:45:55 UTC 
I think this can be fixed later. Yeah, lot more important bugs to be fixed!!
Comment 3 John Baker 2008-08-29 09:56:06 UTC 
I think this is a rare use case, downgrading
Comment 4 Jiri Skrivanek 2009-06-17 13:20:53 UTC 
Fixed with issue 62716.