Resolved bugs still unresolved? [message #1726029] |
Wed, 09 March 2016 02:06  |
Eclipse User |
|
|
|
Not all of us are software engineers.
But a simple drag and drop of a JLabel or JText onto a FormLayout shouldn't lock up the design software or require that someone be an engineer to figure it out. It shouldn't even be an issue by now. Eclipse and WIndowBuilder has been around for years.
A bug was reported "Windowbuilder crashed after Java Upgrade [message #1438556] 06 October 2014".
It has been documented as bug 440411
There have been numerous bugs reported and marked as duplicate regarding this issue.
Even though I have uninstalled and reinstalled JDK1.8 and windowbuilder, tried using older versions, checked for new versions, spent hours searching internet forums (which is my only resource), I have been unable to find any kind of solution other than
"this bug has been reported and a workaround was introduced."
After more hours of internet and forum searching, I learned the workaround was introduced in the "integrated version" which appears to be the latest version.
My code works, I am copying it from a tutorial about JDBC so I can't even take credit for that.
But the problem still exists. Every time I make a change to the project, WindowBuilder locks up and I get the "WindowBuilder has encountered an unexpected internal error."
There doesn't seem to be any solution to this bug. Other than restarting Eclipse every couple of minutes.
|
|
|
|
|
|
|
Re: Resolved bugs still unresolved? [message #1726283 is a reply to message #1726277] |
Fri, 11 March 2016 00:24   |
Eclipse User |
|
|
|
Uploaded and installed Mars. Installer was super easy to use.
BUT, still have the same problem.
I used the same workspace (default) that Kepler was using. I received a warning that the workspace would be unusable with older versions. (I did backup the old workspace somewhere else).
I then used the import wizard to import the project into Eclipse from the same workspace.
I deleted the original class which was written in the Kepler version and started over creating a new JPanel.
I added the formlayout tool.
Then a JLabel field.
Now I wanted to add a JTextField.
That's when the error occurred. Same as before.
Internal Error
WindowBuilder encountered unexpected internal error.
This could be caused by a WindowBuilder bug or by a misconfiguration issue, conflict, partial update, etc.
java.lang.Error: new FormLayout(new ColumnSpec[] { com.jgoodies.forms.layout.FormSpecs.RELATED_GAP_COLSPEC, com.jgoodies.forms.layout.FormSpecs.DEFAULT_COLSPEC,}, new RowSpec[] { com.jgoodies.forms.layout.FormSpecs.RELATED_GAP_ROWSPEC, com.jgoodies.forms.layout.FormSpecs.DEFAULT_ROWSPEC,})
There are a lot of source code errors showing up regarding jgoodies FormSpecs not being resolved to a variable. All my google searches referenced problems in 2014 or older.
All the code was generated by windowbuilder and/or Eclipse.
Windows 10
Eclipse IDE for Java Developers 4.5.2.20160218-0600
Eclipse Java Development Tools 3.11.2.v20160212-1500
Eclipse Platform 4.5.2.v20160212-1500
Swing Designer 1.8.0r45x201506110826
WindowBuilder Core 1.8.0r45x201506110820
The problem doesn't seem to be occurring using a miglayout instead of formlayout.
I've included the bug report and the log file.
[Updated on: Fri, 11 March 2016 01:21] by Moderator
|
|
|
|
Re: Resolved bugs still unresolved? [message #1726855 is a reply to message #1726602] |
Wed, 16 March 2016 23:25  |
Eclipse User |
|
|
|
Guess I meant the same problem is the project locks up whenever I tried to add a JTextbox or JLabel to a FormLayout with WindowBuilder
I think it should be noted that FormLayout should be avoided when creating a GUI with WindowBuilder and possibly removed from the Pallete as an option. Especially with the up to date versions.
For the layperson trying to follow an older step by step tutorial which may use FormLayout it could save a lot of time.
[Updated on: Fri, 18 March 2016 00:35] by Moderator
|
|
|
Powered by
FUDForum. Page generated in 0.06600 seconds