Community
Participate
Working Groups
When a drag'n'drop operation is in progress and the cursor stops over a tree node, it is supposed to expand to allow the user to select a drop target from a subnode. This however doesn't work as expected when a DeferredTreeContentManager is used in the tree viewer's content provider. Steps to reproduce: - check out org.eclipse.ui.examples.job project from the Eclipse CVS - open org.eclipse.ui.examples.jobs.views.LazyTreeView class and put these lines at the end of createPartControl() method: Transfer[] transfers = new Transfer[] {TextTransfer.getInstance()}; viewer.addDragSupport(DND.DROP_MOVE, transfers, new DragSourceAdapter()); viewer.addDropSupport(DND.DROP_MOVE, transfers, new DropTargetAdapter() { public void dragOver(DropTargetEvent event) { event.feedback = DND.FEEDBACK_SELECT | DND.FEEDBACK_EXPAND; } }); - start runtime workbench - open Lazy Trees view - drag any item then stop the cursor over any item that hasn't been expanded yet Notice that the "Pending..." node appears under the selected node but nothing else happens until the drag'n'drop operation is over. This prevents the user from selecting a subnode. The subnodes appear as soon as the mouse button is released or the operation is cancelled.
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.