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 209525 - AssertionError at org.netbeans.modules.form.layoutdesign.LayoutAligner.hasAlignmentInParent
Summary: AssertionError at org.netbeans.modules.form.layoutdesign.LayoutAligner.hasAli...
Status: RESOLVED INCOMPLETE
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-13 15:14 UTC by Michel Graciano
Modified: 2012-04-17 09:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 110992


Attachments
stacktrace (3.65 KB, text/plain)
2012-03-13 15:14 UTC, Michel Graciano
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michel Graciano 2012-03-13 15:14:52 UTC
Build: NetBeans IDE Dev (Build 20120307-71a4e5e49009)
VM: Java HotSpot(TM) Client VM, 22.1-b02, Java(TM) SE Runtime Environment, 1.7.0_03-b04
OS: Linux

User Comments:
dunklenmeistek: I've just settig 3 components aligned left




Stacktrace: 
java.lang.AssertionError
   at org.netbeans.modules.form.layoutdesign.LayoutAligner.hasAlignmentInParent(LayoutAligner.java:1097)
   at org.netbeans.modules.form.layoutdesign.LayoutAligner.alignedIntervals(LayoutAligner.java:1060)
   at org.netbeans.modules.form.layoutdesign.LayoutAligner.transferedComponents(LayoutAligner.java:834)
   at org.netbeans.modules.form.layoutdesign.LayoutAligner.transferToParallelParent(LayoutAligner.java:576)
   at org.netbeans.modules.form.layoutdesign.LayoutAligner.alignIntervals(LayoutAligner.java:96)
   at org.netbeans.modules.form.layoutdesign.LayoutDesigner.align(LayoutDesigner.java:3377)
Comment 1 Michel Graciano 2012-03-13 15:14:55 UTC
Created attachment 116676 [details]
stacktrace
Comment 2 Jan Stola 2012-04-17 09:26:23 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 this problem? 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 the lead to the exception. Thank you in advance.