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 34483

Summary:	NPE when DnD
Product:	platform	Reporter:	ehucka <ehucka>
Component:	Explorer	Assignee:	Jiri Rechtacek <jrechtacek>
Status:	VERIFIED FIXED
Severity:	blocker	Keywords:	JDK_SPECIFIC
Priority:	P2
Version:	3.x
Hardware:	PC
OS:	Windows ME/2000
Issue Type:	DEFECT	Exception Reporter:
Attachments:	Packed ide.log. proposed patch jar file to ensure fix on w2k

Description ehucka 2003-06-19 09:36:07 UTC

NB Build 200306160100
JDK 1.4.1_02
W2K

Durring the Form editing I cannot use Drag and
drop functions in Component inspector. It doesn't
position dragged component and doesn't put it to
any position.
And a lot of NPEs are thrown (see Attachement).

Comment 1 ehucka 2003-06-19 09:37:10 UTC

Created attachment 10733 [details]
Packed ide.log.

Comment 2 Jiri Rechtacek 2003-06-23 20:21:55 UTC

NPE at TreeViewDropSupport.doDragOver(225)
 at TreeViewDropSupport.dragOver(120)
 at  DropTarget.dragOver(356)

It'll be investigated ASAP what's wrong.

Comment 3 Lukas Hasik 2003-08-05 14:33:52 UTC

only on windows. nb40dev - 200307280100

D'n'D starts work again when you move with cursor (still dragging)
outside of window (Explorer)

Comment 4 Jiri Rechtacek 2003-08-12 12:48:24 UTC

*** Issue 34507 has been marked as a duplicate of this issue. ***

Comment 5 Jiri Rechtacek 2003-10-12 21:32:19 UTC

Created attachment 11838 [details]
proposed patch

Comment 6 Jiri Rechtacek 2003-10-12 21:33:25 UTC

Created attachment 11839 [details]
jar file to ensure fix on w2k

Comment 7 Lukas Hasik 2003-10-15 16:05:22 UTC

patch tested - looks ok.

the bug doesn't occure on jdk 1.4.2

Comment 8 Jiri Rechtacek 2003-10-17 09:08:19 UTC

fixed in main trunk,
openide/src/org/openide/explorer/view/TreeViewDropSupport.java, rev.1.35

Added check if glass pane has been stored. The problem only in
jdk1.4.1 on w2k becuase DnD framework could call dragOver() and
dragEnter() in bad order, jdk1.4.2 has fixed it.

Comment 9 Jiri Rechtacek 2003-10-29 10:35:14 UTC

*** Issue 36863 has been marked as a duplicate of this issue. ***

Comment 10 Jiri Rechtacek 2003-10-29 10:48:28 UTC

*** Issue 36863 has been marked as a duplicate of this issue. ***

Comment 11 ehucka 2004-02-23 13:02:29 UTC

Verified.