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 58698 - no component can be added to a form
Summary: no component can be added to a form
Status: VERIFIED DUPLICATE of bug 58695
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Natural Layout (show other bugs)
Version: 5.x
Hardware: Sun All
: P1 blocker (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-09 12:40 UTC by Max Sauer
Modified: 2005-09-05 09:30 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
project, gzipped (121.45 KB, application/x-gzip)
2005-05-09 12:42 UTC, Max Sauer
Details
screenshot (108.81 KB, image/png)
2005-05-09 12:43 UTC, Max Sauer
Details
messages.log file (32.84 KB, text/plain)
2005-05-09 12:44 UTC, Max Sauer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Max Sauer 2005-05-09 12:40:56 UTC
I have a test case, in which no component could be added to a form.
An exception (
java.lang.AssertionError
	at
org.netbeans.modules.form.layoutdesign.LayoutRegion.overlap(LayoutRegion.java:314)
	at
org.netbeans.modules.form.layoutdesign.LayoutDragger.scanLayoutForNextTo(LayoutDragger.java:437)
	at ...)

always occures.

Steps to reproduce this test case:
----------------------------------
0) Have a fresh userdirectory.
1) Open the project in the attachement via the "File->Open Project" command.
2) In package formstudy, double-click the Frame3.java to open it.
3) Try to add a new component (eg. a JButton).
4) The exception pops-up.

System Specs:
------------
NB 4.2dev 200505081800
/form_prototype/20050509
j2sdk1.4.2_05

I'm ataching the project and a screeenshot.
Comment 1 Max Sauer 2005-05-09 12:42:46 UTC
Created attachment 22034 [details]
project, gzipped
Comment 2 Max Sauer 2005-05-09 12:43:56 UTC
Created attachment 22035 [details]
screenshot
Comment 3 Max Sauer 2005-05-09 12:44:45 UTC
Created attachment 22036 [details]
messages.log file
Comment 4 _ lcincura 2005-05-09 13:34:07 UTC
The only workaround is to start the form again from scratch. This is complete
data loss, thus increasing priority to P1.
Comment 5 Jan Stola 2005-05-09 16:48:14 UTC
The attached form is already in a wrong state. Looking at the generated code,
there is a snippet:

                    .add(68, 68, 68)
                    .add(12, 246, Short.MAX_VALUE))

This means two consecutive gaps at the trailing end of the vertical layout
which is wrong.

Marking as duplicate of issue 58695, but feel free to reopen if you are
able to reproduce how to obtain this state (we will check whether it
is really caused by the same bug as issue 58695).

*** This issue has been marked as a duplicate of 58695 ***
Comment 6 Max Sauer 2005-08-30 09:00:18 UTC
Verified duplicate.