This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 74737 - D&D ability in the Navigator window
Summary: D&D ability in the Navigator window
Alias: None
Product: platform
Classification: Unclassified
Component: Navigator (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: David Simonek
Keywords: UI
Depends on:
Blocks: 93713
  Show dependency tree
Reported: 2006-04-10 16:46 UTC by dpavlica
Modified: 2008-12-22 11:51 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description dpavlica 2006-04-10 16:46:56 UTC
We try to merge Outline window with the Navigator in Creator and we need 
Drag&Drop in the Navigator window for reordering items inside.
Comment 1 David Simonek 2006-04-10 17:18:40 UTC
DnD *is enabled* in navigator. All navigator panels are regular AWT and Swing
components. So DnD works exactly the same way as in other AWT or Swing app/demo.

This means that guys in Creator will be able to activate DnD on their navigator
panel using standard DnD programming, explained in JDK javadoc of awt.dnd
package. There is no need for special support, AFAIK.

Please reopen with more details if I got smt wrong, thanks.  
Comment 2 dpavlica 2006-04-11 17:43:58 UTC
I know, but it seems logical to have it consistent in the Navigator in Netbeans too.
I remember it was implemented there at the start and then the "reordering ability by D&D" was removed. 
Might I ask what was the reason for removing it?
Comment 3 David Simonek 2007-03-14 20:45:59 UTC
This is misunderstanding, we are talking about different things...


- D&D for reordering in *java source* navigation is wrong idea, because methods
and fields are not sorted in navigator tree like in the source itself. So
dragging will produce undefined and unacceptable results.

- D&D in "Outline" view or any other view from visual web component is possible,
and must be implemented directly by the Outline component, as described in my
first response.

Closing as invalid, hopefully now it's all clear.