Summary: | Tree.getSelection() could be better ordered | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Chris McLaren <csmclaren> |
Component: | SWT | Assignee: | Steve Northover <steve_northover> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | bokowski, Silenio_Quarti |
Version: | 2.0 | ||
Target Milestone: | 3.3 M2 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: | |||
Bug Depends on: | |||
Bug Blocks: | 153105 |
Description
Chris McLaren
2002-05-30 16:41:30 EDT
For multiselect trees, it would be helpful if the result of Tree.getSelection() was guaranteed to be in an intuitive order from a user perspective, either top down in the tree or in order of selection by the user. it seems that .getSelection() returns the selection in the order of the items field, which does not necessarily meet either of those criteria in a lazily populating or mutating tree. This makes sense. I'm not sure if we can do anything about this for R2.0, but we'll investigate. It does make sense but we cannot guarantee the order of the selection on every platform. I believe it's dangerous to try to enforce an order. It could lead to performance problems or put us in a situation where there is no native API to implement what we want when porting to new platforms. Reopening for investigation. Fixed > 20060828 |