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.
[ BUILD # : beta ] [ JDK VERSION : 1.5.0_04 ] I`m sending to you a project with 4 forms. And what you have to do to cause some unexpect behaviour... With Form2 and 3 i got exceptions... On 1 and 4 I could not be able to create the design i wanted. Form 1 - Try to align the end of JTextField5 with the end of JTextField1 Form 2 - Error when resing Form 3 - Move the Table to align its top with the botton of the two buttons. Resize the botton of the form to align with the botton of the table. And finally try to resize the form -> Assertion Error... Form 4 - Try to align the JPanel with the first combobox ...
Created attachment 25776 [details] Project with the forms
In Form 3 vertical resizability for the table should be set. Then it works fine. In Form 4 aligning the panel left with either combobox causes rest of the components to move right. This could be investigated. Other cases work, no exception.
The first three test cases has been fixed. The last one (Form 4) is weird => lowering priority to P4.
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. We apologize for any inconvenience. Thank you. The NetBeans Team
Still valid. The test case is to move panel in Form4 so it left-aligns with the first combobox. This causes all components moving to right side.
(In reply to comment #3) > The first three test cases has been fixed. The 4th test case still valid in: Product Version: NetBeans IDE 7.1 Beta (Build 201109252201) Java: 1.7.0; Java HotSpot(TM) Client VM 21.0-b17 System: Linux version 2.6.38-11-generic running on i386; UTF-8; en_US (nb)
As for the last test case in this bug, I can't reproduce it current dev build (but can reproduce in NB 7.0). So I think we can finally close this as fixed.