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 194442

Summary:	[70cat] AssertionError at org.netbeans.modules.form.layoutdesign.LayoutDesigner.getDraggableComponents
Product:	guibuilder	Reporter:	Chiana
Component:	Code	Assignee:	issues@guibuilder <issues>
Status:	RESOLVED INCOMPLETE
Severity:	normal	CC:	areeda, sidlo
Priority:	P3
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:	175959
Attachments:	stacktrace

Description Chiana 2011-01-18 17:51:35 UTC

This bug was originally marked as duplicate of bug 159863, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE Dev (Build nbms-and-javadoc-6477-on-110117)
VM: Java HotSpot(TM) 64-Bit Server VM, 19.0-b09, Java(TM) SE Runtime Environment, 1.6.0_23-b05
OS: Windows 7

User Comments:
Chiana: Found the panel, it is at the top-left with a size null, got this when I tried to enlarge it by dragging one of the corners.

areeda: moving jlabel in free design dialog

sidlo: arange gui

Chiana: Small, wery small (0,0) panel that is stuck in the upper left corner and refuses to be dealt with...
I note that there is one component inserted in this panel that is WAY outside it and MUCH bigger.




Stacktrace: 
java.lang.AssertionError
   at org.netbeans.modules.form.layoutdesign.LayoutDesigner.getDraggableComponents(LayoutDesigner.java:387)
   at org.netbeans.modules.form.HandleLayer.getComponentsToDrag(HandleLayer.java:1229)
   at org.netbeans.modules.form.HandleLayer.mouseDragged(HandleLayer.java:1981)
   at java.awt.AWTEventMulticaster.mouseDragged(AWTEventMulticaster.java:302)
   at java.awt.Component.processMouseMotionEvent(Component.java:6315)
   at javax.swing.JComponent.processMouseMotionEvent(JComponent.java:3285)

Comment 1 Chiana 2011-01-18 17:51:39 UTC

Created attachment 105108 [details]
stacktrace

Comment 2 Chiana 2011-01-18 18:06:11 UTC

See also bug 163203 that is apparently related

Comment 3 Jan Stola 2011-11-04 10:33:57 UTC

I am sorry, I am not able to reproduce this issue and the attached stack-trace is not sufficient to track the problem down. Are you still able to reproduce it? If so, could you, please, provide more details? It would be ideal to attach the problematic form (both .java and .form files) saved in the last good state and describe _exact_ steps that lead to this exception. Thank you in advance.