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.
This bug was originally marked as duplicate of bug 210038, 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 201208300001) VM: Java HotSpot(TM) 64-Bit Server VM, 23.1-b03, Java(TM) SE Runtime Environment, 1.7.0_05-b05 OS: Windows 7 User Comments: GUEST: resizing a text field, to align right side with another mienamoo: Resizing a button on a panel in the GUI builder. Stacktrace: java.lang.AssertionError at org.netbeans.modules.form.layoutdesign.LayoutFeeder.addToGroup(LayoutFeeder.java:1290) at org.netbeans.modules.form.layoutdesign.LayoutFeeder.addInterval(LayoutFeeder.java:1179) at org.netbeans.modules.form.layoutdesign.LayoutFeeder.add(LayoutFeeder.java:470) at org.netbeans.modules.form.layoutdesign.LayoutDesigner.addComponents(LayoutDesigner.java:850) at org.netbeans.modules.form.layoutdesign.LayoutDesigner.endMoving(LayoutDesigner.java:811) at org.netbeans.modules.form.HandleLayer$ResizeComponentDrag.end(HandleLayer.java:3133)
Created attachment 123730 [details] stacktrace
Any chance to provide the GUI form where this error happened? Or a sample form where it can also be reproduced, with exact steps how to reproduce it from the "last good state"? This kind of errors are very sensitive to the exact specific layout state and performed operation, and are really hard to fix without reproducing. So an reproducible test case would help us a lot. Thanks.
I will see what I can do. I always run into the difficult to reproduce issues somehow. :-) One interesting thing I can add right now is that resizing the button to the one side caused the issue and to the other not.
Note that when such an error happens, the actual mouse operation is canceled (the change does not happen, the state returns back). So if you save the form at this moment and describe what exactly you did, you basically have the reproducible test case. You can also try again to see if it's still happening. Sometimes even single pixels may matter, so must be precise. If you can't hit it again, just do undo and repeat from the same initial state from which it happened first time. Thanks for cooperation.
I am not able to reproduce it this morning. :(
*** Bug 231671 has been marked as a duplicate of this bug. ***
Additional diagnostic code was added to 7.4, this defect now has a different exception stack trace and is tracked as bug 237321. Closing this bug.