Community
Participate
Working Groups
consider three projects, say org.eclipse.ant, org.eclipse.lucene, and org.eclipse.xerces. open packages view expand org.eclipse.lucene, then org.eclipse.xerces, then org.eclipse.ant. now select org.eclipse.ant/about.html, org.eclipse.lucene/about.html, and org.eclipse.xerces/about.html. from the task view, filter on 'any resource in same project'. click new task. notice the new task dialog shows the folder as org.eclipse.lucene. one might expect it to be org.eclipse.ant/about.html as it is both first in the top down order as well as the anchor selection, or perhaps org.eclipse.xerces/about.html as it is the lead selection.
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