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: | Update tasklist children only in EQ | ||
|---|---|---|---|
| Product: | platform | Reporter: | Jesse Glick <jglick> |
| Component: | Action Items | Assignee: | tasklist-issues@contrib <tasklist-issues> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | Keywords: | THREAD |
| Priority: | P2 | ||
| Version: | 3.x | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Bug Depends on: | |||
| Bug Blocks: | 37802 | ||
| Attachments: | Suggested patch | ||
|
Description
Jesse Glick
2003-12-08 16:48:01 UTC
Created attachment 12462 [details]
Suggested patch
Since #37802 was pushed off into the future, treating this as the visible defect. What? Should any Children.Key client wrap setKeys call to Runnable? Why it's not done in setKeys directly. TTV custody. OK, just another workaround. However rather early in dev cycle. In nodes_eq_35833, Children.Keys.setKeys *does* automatically replan itself to EQ. In that branch it has to because children can only be accessed in EQ. In the trunk this is not generally required and you can use any thread, under Children.MUTEX, and e.g. BeanTreeView handles it fine; but it seems TTV is buggy in its use of VisualizerChildren, and it seems that restricting yourself to EQ-only access (which is anyway the long-term goal) avoids those bugs. Do you think you could increment tasklist/core/manifest.mf so that this critical workaround gets published on AU? The current AU version is org.netbeans.modules.tasklist.core/1 [1.15 200312111900] which does not have the fix. Please, reporter, could you verify fixed issues. Thanks a lot. |