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.
Summary: | Unneeded refreshing of node in TreeView | ||
---|---|---|---|
Product: | versioncontrol | Reporter: | mslama <mslama> |
Component: | CVS | Assignee: | issues@versioncontrol <issues> |
Status: | NEW --- | ||
Severity: | blocker | CC: | jtulach |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 115358 | ||
Attachments: | Complete call stack |
Description
mslama
2007-10-02 11:27:37 UTC
There is too many VisibilityQuery ChangeEvents when deleting folder structure. According to Jarda surrounding line: private static void refreshVisibility() { if (instance != null) { instance.refreshVisibilityTask.schedule(100); } } by AtomicAction should solve this problem as events would be fired after whole delete operation would be finished. Created attachment 49980 [details]
Complete call stack
What is wrong with the stacktrace? It does not imply that the refresh is actually run - it is only being scheduled. I can increase scheduling delay to 1000 or so, we'll see if that helps. Regarding AtomicAction; this would have to be done several layers above CVS and synchronous callbacks involved here such as doDelete() would not be affected anyway. Just try steps described above and you will see what is wrong. Too many events are comming to Favorites from VisibilityQuery during delete. *** Issue 118268 has been marked as a duplicate of this issue. *** |