Community
Participate
Working Groups
It would be much more useful if the order of elements in StructuredSelection were the same as the one produced by associated ContentProvider (or physical order of treeItems in the Tree widget). Even items on the same level seem to be arranged randomly (sometimes the sequence of selection makes the difference, such as one-by-one, bottom-to-top, top-to-bottom etc).
SWT does not guarantee the order in which selected tree items are returned, and TreeViewer only wraps the selection returned by SWT. This is the Javadoc of Tree.getSelection(): * Returns an array of <code>TreeItem</code>s that are currently * selected in the receiver. The order of the items is unspecified. * An empty array indicates that no items are selected. We could try and sort the selected items before returning the selection, but I would prefer leaving the behaviour as is (i.e., no sorting) because this is consistent with all viewer classes. I'm closing this as WONTFIX, but please feel free to reopen if you have a specific use case that justifies the additional overhead of sorting (could the sorting be done in client code?)
Our product displays contents of EMF model in a tree where the order of nodes is dictated by the model. The editor allows for manipulation of some elements, for example re-parenting. It is important that when elements are moved, their order remains unchanged. We, of course, sort selection every time we need it. Additionally, our product is extendable, meaning that other tools can contribute behavior (such as new protocols) to a test. Therefore, I persive the need to sort the selection *every* time it is needed, and the need to enforce this requirement on contributions, as an unnecessary and hard-to-control burden. I would prefer it to arrive sorted. For people, who do not care, there will be no difference; for others, it will be a relief. If there is code out there that *depends* on the order being *random*, some sort of flag can be used to indicate the required sorting? In general, I fail to see why, on JFACE level, the out-order (from structured selection) is different from in-order (from ContentProvider).
Hitesh is now responsible for watching bugs in the [Viewers] component area.
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.
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie.
