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 39702 - [36cat] Importing project freezes the interface
Summary: [36cat] Importing project freezes the interface
Status: VERIFIED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Autoupdate (show other bugs)
Version: 3.x
Hardware: PC Windows XP
: P3 blocker with 1 vote (vote)
Assignee: Jiri Rechtacek
URL:
Keywords: UI
Depends on:
Blocks:
 
Reported: 2004-02-06 15:22 UTC by carcassi
Modified: 2005-12-20 16:04 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
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 carcassi 2004-02-06 15:22:45 UTC 
[ JDK VERSION : J2SE 1.4.2_02 ]

I had 20 projects to import, and the dialog basically froze when importing (it wouldn't even repaint). The project was successfull, but it took a long time: an average user would think that it's not working.

A more responsive dialog, with a progress indicator, would make things much better.
Comment 1 zikmund 2004-02-09 10:35:06 UTC 
It seems to be autoupdate problem.
Comment 2 Jiri Rechtacek 2004-02-11 16:29:40 UTC 
You are right, maybe a progress dialog will be better but it's a UI
change not implementable in this phase nb3.6 development. Thanks for
feedback, will be keep in mind as enhancement for next release.
Comment 3 Jan Chalupa 2004-02-23 09:26:58 UTC 
I may be missing something, but I don't think this is an autoupdate
issue. Importing of settings is don in core.
Comment 4 Jiri Rechtacek 2004-12-08 14:54:22 UTC 
Jan, you are right this not Autoupdate's problem but core's.
Because, the new one project's support has been provided in NB4.0,
this issue is obsolete now, won't be fixed.
Comment 5 Marian Mirilovic 2005-12-20 16:04:30 UTC 
This issue was solved long time ago. Because nobody has reopened it neither
added comments, we are verifying/closing it now. 
If you are still able to reproduce the problem, please reopen. 

Thanks in advance.