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 253743

Summary: AssertionError at org.netbeans.modules.form.layoutdesign.LayoutInterval.getCurrentSpace
Product: guibuilder Reporter: mienamoo
Component: CodeAssignee: issues@guibuilder <issues>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: P3    
Version: 8.1   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter: 182840
Attachments: stacktrace

Description mienamoo 2015-07-24 14:02:38 UTC
Build: NetBeans IDE 8.1 Beta (Build 201507231027)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.45-b02, Java(TM) SE Runtime Environment, 1.8.0_45-b14
OS: Windows 8

User Comments:
GUEST: layout problem

mienamoo: I was executing the steps of this test:
http://services.netbeans.org/synergy/client/app/index.html#/case/1306/suite/1073/v/1

In step 5, when dragging the components outside of the panel, this exception occurred.

GUEST: dragging multiple items [snapping to default sized horizontal separator]

GUEST: moving 3 text fields

GUEST: laying out GUI




Stacktrace: 
java.lang.AssertionError
   at org.netbeans.modules.form.layoutdesign.LayoutInterval.getCurrentSpace(LayoutInterval.java:503)
   at org.netbeans.modules.form.layoutdesign.LayoutInterval.getCurrentPositions(LayoutInterval.java:1024)
   at org.netbeans.modules.form.layoutdesign.LayoutDesigner.restrictedCopy(LayoutDesigner.java:1142)
   at org.netbeans.modules.form.layoutdesign.LayoutDesigner.restrictedCopy(LayoutDesigner.java:1045)
   at org.netbeans.modules.form.layoutdesign.LayoutDesigner.restrictedCopy(LayoutDesigner.java:1045)
   at org.netbeans.modules.form.layoutdesign.LayoutDesigner.endMoving(LayoutDesigner.java:799)
Comment 1 mienamoo 2015-07-24 14:02:41 UTC
Created attachment 154857 [details]
stacktrace
Comment 2 Tomas Pavek 2015-09-09 16:09:22 UTC
This looks very similar to bug 253745 (including the fact that people report multiple component dragging).

*** This bug has been marked as a duplicate of bug 253745 ***