Bugzilla – Full Text Bug Listing
| Summary: | Inserting TreeItem at a specified index | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Hitesh <hsoliwal> | ||||
| Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> | ||||
| Status: | NEW --- | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | Keywords: | performance | ||||
| Version: | 3.6 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. |
Created attachment 174141 [details] Snippet and Profiler Screenshots The difference between creating a TreeItem at a specified index and creating at the lastIndex appears to be inexplicably large. It seems to be unaffected even if one created hundreds or thousands of items consecutively at same index or incrementing/decrementing index - the cost remains the same. It would be highly desirable if this gap could be reduced. Particularly in place where large structural changes can be avoided while refreshing. I am attaching some profiler screenshots and a snippet.