Closed CindyCASC closed 1 year ago
I remember seeing a similar error a few months ago, but I was never able to reliably reproduce it. Would it be possible for you to provide a small example? I've just created a simple panel and there drag & drop works with the GridBagLayout, so I assume it only shows up under certain circumstances.
Which WindowBuilder version did you upgrade from?
Hello Patrick,
Thank you for your response. I hope the information provided below is helpful.
I have two versions of Eclipse currently installed on my desktop PC (Neon and 2023-06) which is running Windows 10 Enterprise. I was using Neon until last fall when I decided to upgrade to 2023-06 but kept Neon just incase I had issues with the new install.
Neon does not have any issues with GridBagLayout. I can add and delete components and navigate thru the Structure gaining focus on the components without any issues. Eclipse Java EE IDE for Web Developers. Version: Neon.3 Release (4.6.3) Build id: 20170314-1500 Java > Compiler > JDK Compliance 1.8 Installed Plugins: Dart Designer Eclipse Enterprise Java and Web Developer Tools 3.8.2 Eclipse JST Server Adapters (Apache Tomcat, JOnAS, J2EE) Luna Eclipsed Web Developer Tools 3.8.2 Maven (Java EE) Integration for Eclipse WTP (Luna/Mars) 1.2.0 Remote System Explorer (SSH, Telnet, FTP and DStore protocols) 3.5.0 TM Terminal 4.0 20150430 (Mars M7) WindowBuilder Nightly Build Nightly @.***
Component allows Cut, Copy, Paste and Delete @. Selected components in the Structure also selects component in the view and does so for any component selected. @.
2023-06 Eclipse IDE for Java Developers (includes Incubating components) Version: 2023-06 (4.28.0) Build id: 20230608-1333 Java > Compiler > JDK Compliance 1.8 Installed Plugins: Buildship Gradle Integration 3.0 EclEmma Java Code Coverage 3.1.7 Eclipse Java Development Tools Latest release Eclipse m2e - Maven support in Eclipse IDE Latest Eclipse Marketplace Client 1.10.0 Eclipse XML Editors and Tools 3.30 EGit - Git Integration for Eclipse 6.0.0 m2e-connector for maven-remote-resources-plugin 0.0.1 TM Terminal CDT 11.2 (2023-06) WindowBuilder Current WindowBuilder Nightly Build Nightly @.***
I have the following issues with 2023-06 -throws exceptions when adding components to GridBagLayout or when trying to rename a component @. This happened on a brand new project with only one or two components on a GridBagLayout panel. @. -Component does not allow Copy, Paste or Delete once added to the panel. @. -Row Delete Contents causes error @. -when selecting a component in the Design tab Structure does not select the component in the panel. lblPosted is selected in the Structure but not in the view. @. -I also get errors like this when switching between open projects that have a GridBagLayout @.
If you need any additional information please let me know.
I don't know if it is a bug or version compatibility issue or designer setup but hopefully this will lead you closer to a solution.
Thank you.
@.*** Cindy Cunningham Programmer Analyst
Email: @.**@.> Phone: 517-442-1981
906 James St, Adrian, MI 49221
www.adriansteel.comhttp://www.adriansteel.com/
From: Patrick Ziegler @.> Sent: Thursday, August 10, 2023 12:59 AM To: eclipse-windowbuilder/windowbuilder @.> Cc: Cindy Cunningham @.>; Author @.> Subject: [EXTERNAL] Re: [eclipse-windowbuilder/windowbuilder] WindowBuilder was not able to show the GUI (Issue #533)
You don't often get email from @.**@.>. Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
I remember seeing a similar error a few months ago, but I was never able to reliably reproduce it. Would it be possible for you to provide a small example? I've just created a simple panel and there drag & drop works with the GridBagLayout, so I assume it only shows up under certain circumstances.
Which WindowBuilder version did you upgrade from?
- Reply to this email directly, view it on GitHubhttps://github.com/eclipse-windowbuilder/windowbuilder/issues/533#issuecomment-1672554713, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAQLGWFU572ECFVQMHJV4VDXURTBBANCNFSM6AAAAAA3J6LRMY. You are receiving this because you authored the thread.Message ID: @.**@.>>
Patrick,
Just incase this helps I added two more screen shots.
Neon @. 2023-06 @.
@.*** Cindy Cunningham Programmer Analyst
Email: @.**@.> Phone: 517-266-5145
906 James St, Adrian, MI 49221
www.adriansteel.comhttp://www.adriansteel.com/
From: Patrick Ziegler @.> Sent: Thursday, August 10, 2023 12:59 AM To: eclipse-windowbuilder/windowbuilder @.> Cc: Cindy Cunningham @.>; Author @.> Subject: [EXTERNAL] Re: [eclipse-windowbuilder/windowbuilder] WindowBuilder was not able to show the GUI (Issue #533)
You don't often get email from @.**@.>. Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
I remember seeing a similar error a few months ago, but I was never able to reliably reproduce it. Would it be possible for you to provide a small example? I've just created a simple panel and there drag & drop works with the GridBagLayout, so I assume it only shows up under certain circumstances.
Which WindowBuilder version did you upgrade from?
- Reply to this email directly, view it on GitHubhttps://github.com/eclipse-windowbuilder/windowbuilder/issues/533#issuecomment-1672554713, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAQLGWFU572ECFVQMHJV4VDXURTBBANCNFSM6AAAAAA3J6LRMY. You are receiving this because you authored the thread.Message ID: @.**@.>>
Patrick,
I must apologize. I was so intent on making sure you had the Eclipse information that I did not send you the example code. I hope this helps.
MyTestApp I added a JTabbedPane and pnlEast with GridBagLayout.
When I try to delete the JTabbedPane I get this error. @.***
I cannot Delete the new label on the pnlEast (GridBagLayout)
If it try to change pnlEast from a GridBagLayout back to FlowLayout or or any other layout I get this error. @.***
@.*** Cindy Cunningham Programmer Analyst
Email: @.**@.> Phone: 517-266-5145
906 James St, Adrian, MI 49221
www.adriansteel.comhttp://www.adriansteel.com/
From: Patrick Ziegler @.> Sent: Thursday, August 10, 2023 12:59 AM To: eclipse-windowbuilder/windowbuilder @.> Cc: Cindy Cunningham @.>; Author @.> Subject: [EXTERNAL] Re: [eclipse-windowbuilder/windowbuilder] WindowBuilder was not able to show the GUI (Issue #533)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
I remember seeing a similar error a few months ago, but I was never able to reliably reproduce it. Would it be possible for you to provide a small example? I've just created a simple panel and there drag & drop works with the GridBagLayout, so I assume it only shows up under certain circumstances.
Which WindowBuilder version did you upgrade from?
- Reply to this email directly, view it on GitHubhttps://github.com/eclipse-windowbuilder/windowbuilder/issues/533#issuecomment-1672554713, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAQLGWFU572ECFVQMHJV4VDXURTBBANCNFSM6AAAAAA3J6LRMY. You are receiving this because you authored the thread.Message ID: @.***>
Patrick,
My Monday is really not starting out well. I forgot to attach the source.
@.*** Cindy Cunningham Programmer Analyst
Email: @.**@.> Phone: 517-266-5145
906 James St, Adrian, MI 49221
www.adriansteel.comhttp://www.adriansteel.com/
From: Patrick Ziegler @.> Sent: Thursday, August 10, 2023 12:59 AM To: eclipse-windowbuilder/windowbuilder @.> Cc: Cindy Cunningham @.>; Author @.> Subject: [EXTERNAL] Re: [eclipse-windowbuilder/windowbuilder] WindowBuilder was not able to show the GUI (Issue #533)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
I remember seeing a similar error a few months ago, but I was never able to reliably reproduce it. Would it be possible for you to provide a small example? I've just created a simple panel and there drag & drop works with the GridBagLayout, so I assume it only shows up under certain circumstances.
Which WindowBuilder version did you upgrade from?
- Reply to this email directly, view it on GitHubhttps://github.com/eclipse-windowbuilder/windowbuilder/issues/533#issuecomment-1672554713, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAQLGWFU572ECFVQMHJV4VDXURTBBANCNFSM6AAAAAA3J6LRMY. You are receiving this because you authored the thread.Message ID: @.***>
Hm, it seems like none of the attachments are uploaded to GitHub if you send them via mail :/
I've tried to reproduce this issue locally over the past few days, but without success. So the source code would be greatly appreciated. It might also help if you could zip the entire project and upload it, given that the culprit might also be some persisted metadata that doesn't play nice.
Patrick,
Hope these attachments help.
Options for saving only offer "Close with comment". Please do not close.
Please keep this open
Patrick,
Attachments uploaded in GitHub but only option was "Close with comment"
Please keep me updated.
Thank you
@.*** Cindy Cunningham Programmer Analyst
Email: @.**@.> Phone: 517-442-1981
906 James St, Adrian, MI 49221
www.adriansteel.comhttp://www.adriansteel.com/
From: Patrick Ziegler @.> Sent: Tuesday, August 15, 2023 2:12 AM To: eclipse-windowbuilder/windowbuilder @.> Cc: Cindy Cunningham @.>; Author @.> Subject: [EXTERNAL] Re: [eclipse-windowbuilder/windowbuilder] WindowBuilder was not able to show the GUI (Issue #533)
You don't often get email from @.**@.>. Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
Hm, it seems like none of the attachments are uploaded to GitHub if you send them via mail :/
I've tried to reproduce this issue locally over the past few days, but without success. So the source code would be greatly appreciated. It might also help if you could zip the entire project and upload it, given that the culprit might also be some persisted metadata that doesn't play nice.
- Reply to this email directly, view it on GitHubhttps://github.com/eclipse-windowbuilder/windowbuilder/issues/533#issuecomment-1678471238, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAQLGWBCL5GWHOI2SHEMX4DXVMHKBANCNFSM6AAAAAA3J6LRMY. You are receiving this because you authored the thread.Message ID: @.**@.>>
Attachments uploaded in GitHub but only option was "Close with comment"
You should be able to attach files via drag & drop and GitHub should automatically upload them.
In any case, I think I have a rough idea what's happening, I just don't understand why it's happening and why it's not happening on my side, even when using your code example.
I've created #546 which hopefully handles this error a little bit more gracefully. If there are no regressions, there should be a build available tomorrow that might fix this problem.
Sounds hopeful.
Thank you for the update.
@.*** Cindy Cunningham Programmer Analyst
Email: @.**@.> Phone: 517-442-1981
906 James St, Adrian, MI 49221
www.adriansteel.comhttp://www.adriansteel.com/
From: Patrick Ziegler @.> Sent: Tuesday, August 15, 2023 2:49 PM To: eclipse-windowbuilder/windowbuilder @.> Cc: Cindy Cunningham @.>; State change @.> Subject: [EXTERNAL] Re: [eclipse-windowbuilder/windowbuilder] WindowBuilder was not able to show the GUI (Issue #533)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
Attachments uploaded in GitHub but only option was "Close with comment"
You should be able to attach files via drag & drop and GitHub should automatically upload them.
[Image removed by sender. image]https://user-images.githubusercontent.com/70652978/260807175-843385a3-5240-4e3a-8db8-071055b7c654.png
In any case, I think I have a rough idea what's happening, I just don't understand why it's happening and why it's not happening on my side, even when using your code example.
I've created #546https://github.com/eclipse-windowbuilder/windowbuilder/pull/546 which hopefully handles this error a little bit more gracefully. If there are no regressions, there should be a build available tomorrow that might fix this problem.
- Reply to this email directly, view it on GitHubhttps://github.com/eclipse-windowbuilder/windowbuilder/issues/533#issuecomment-1679427630, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAQLGWBMJKXWCEBZ66P7QSDXVPADTANCNFSM6AAAAAA3J6LRMY. You are receiving this because you modified the open/close state.Message ID: @.***>
Patrick,
The patch you created appears to prevent the hard errors.
The issue still remains in GridBagLayout I cannot delete any components that have been added.
It will not stop development because I can edit directly in the source but I sure would be nice to have that functionality back.
@.*** Cindy Cunningham Programmer Analyst
Email: @.**@.> Phone: 517-442-1981
906 James St, Adrian, MI 49221
www.adriansteel.comhttp://www.adriansteel.com/
From: Patrick Ziegler @.> Sent: Tuesday, August 15, 2023 2:49 PM To: eclipse-windowbuilder/windowbuilder @.> Cc: Cindy Cunningham @.>; State change @.> Subject: [EXTERNAL] Re: [eclipse-windowbuilder/windowbuilder] WindowBuilder was not able to show the GUI (Issue #533)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
Attachments uploaded in GitHub but only option was "Close with comment"
You should be able to attach files via drag & drop and GitHub should automatically upload them.
[Image removed by sender. image]https://user-images.githubusercontent.com/70652978/260807175-843385a3-5240-4e3a-8db8-071055b7c654.png
In any case, I think I have a rough idea what's happening, I just don't understand why it's happening and why it's not happening on my side, even when using your code example.
I've created #546https://github.com/eclipse-windowbuilder/windowbuilder/pull/546 which hopefully handles this error a little bit more gracefully. If there are no regressions, there should be a build available tomorrow that might fix this problem.
- Reply to this email directly, view it on GitHubhttps://github.com/eclipse-windowbuilder/windowbuilder/issues/533#issuecomment-1679427630, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAQLGWBMJKXWCEBZ66P7QSDXVPADTANCNFSM6AAAAAA3J6LRMY. You are receiving this because you modified the open/close state.Message ID: @.***>
Hi Cindy. Sorry, I lost track of this problem. But the general problem is that I just can't reproduce this exception, so I have a really hard time coming up with a solution...
Perhaps let's try to reproduce this in a more controlled environment. I think you're using the Eclipse IDE. Can you instead try to download and install the Eclipse SDK? https://download.eclipse.org/eclipse/downloads/drops4/R-4.28-202306050440/
Just download & unpack the zip archive for your operating system.
Then install the latest WindowBuilder milestone https://download.eclipse.org/windowbuilder/updates/milestone/S202309051601/
Then open this test widget:
package com.adriansteel.test;
import java.awt.GraphicsConfiguration;
import java.awt.HeadlessException;
import javax.swing.JPanel;
import java.awt.BorderLayout;
import java.awt.GridBagLayout;
import javax.swing.JTabbedPane;
import javax.swing.JTextField;
import javax.swing.border.EmptyBorder;
import javax.swing.JButton;
import javax.swing.JFrame;
import java.awt.GridBagConstraints;
import java.awt.FlowLayout;
import javax.swing.JLabel;
import java.awt.Insets;
public class MyTestApp extends JFrame {
private JPanel pnlNorth;
private JTabbedPane tabbedPane;
private JTextField textField;
private JPanel pnlEast;
private JPanel pnlSouth;
private JButton btnNewButton;
private JLabel lblNewLabel;
private JLabel lblNewLabel_1;
public MyTestApp() throws HeadlessException {
getContentPane().add(getPnlNorth(), BorderLayout.NORTH);
getContentPane().add(getTabbedPane(), BorderLayout.CENTER);
getContentPane().add(getPnlEast(), BorderLayout.EAST);
getContentPane().add(getPnlSouth(), BorderLayout.SOUTH);
// TODO Auto-generated constructor stub
}
public MyTestApp(GraphicsConfiguration arg0) {
super(arg0);
// TODO Auto-generated constructor stub
}
public MyTestApp(String arg0) throws HeadlessException {
super(arg0);
// TODO Auto-generated constructor stub
}
public MyTestApp(String arg0, GraphicsConfiguration arg1) {
super(arg0, arg1);
// TODO Auto-generated constructor stub
}
public static void main(String[] args) {
// TODO Auto-generated method stub
}
private JPanel getPnlNorth() {
if (pnlNorth == null) {
pnlNorth = new JPanel();
pnlNorth.setLayout(new BorderLayout(0, 0));
pnlNorth.add(getTextField(), BorderLayout.NORTH);
}
return pnlNorth;
}
private JTabbedPane getTabbedPane() {
if (tabbedPane == null) {
tabbedPane = new JTabbedPane(JTabbedPane.TOP);
}
return tabbedPane;
}
private JTextField getTextField() {
if (textField == null) {
textField = new JTextField();
}
return textField;
}
private JPanel getPnlEast() {
if (pnlEast == null) {
pnlEast = new JPanel();
GridBagLayout gbl_pnlEast = new GridBagLayout();
gbl_pnlEast.columnWidths = new int[] {0, 0};
gbl_pnlEast.rowHeights = new int[] {0, 0, 0};
gbl_pnlEast.columnWeights = new double[]{0.0, Double.MIN_VALUE};
gbl_pnlEast.rowWeights = new double[]{0.0, 0.0, Double.MIN_VALUE};
pnlEast.setLayout(gbl_pnlEast);
GridBagConstraints gbc_lblNewLabel = new GridBagConstraints();
gbc_lblNewLabel.insets = new Insets(0, 0, 5, 0);
gbc_lblNewLabel.gridx = 0;
gbc_lblNewLabel.gridy = 0;
pnlEast.add(getLblNewLabel(), gbc_lblNewLabel);
GridBagConstraints gbc_lblNewLabel_1 = new GridBagConstraints();
gbc_lblNewLabel_1.gridx = 0;
gbc_lblNewLabel_1.gridy = 1;
pnlEast.add(getLblNewLabel_1(), gbc_lblNewLabel_1);
}
return pnlEast;
}
private JPanel getPnlSouth() {
if (pnlSouth == null) {
pnlSouth = new JPanel();
pnlSouth.add(getBtnNewButton());
}
return pnlSouth;
}
private JButton getBtnNewButton() {
if (btnNewButton == null) {
btnNewButton = new JButton("New button");
}
return btnNewButton;
}
private JLabel getLblNewLabel() {
if (lblNewLabel == null) {
lblNewLabel = new JLabel("New label");
}
return lblNewLabel;
}
private JLabel getLblNewLabel_1() {
if (lblNewLabel_1 == null) {
lblNewLabel_1 = new JLabel("New label");
}
return lblNewLabel_1;
}
}
If you open this in design page and try to delete "New label", does the error still show up?
Patrick,
I downloaded but could not install the JDK you listed.
I am getting "Version 1.8.0_144 of the JVM is not suitable for this product. Version 17 or greater is required."
I don't know my next step. I may want to install on a different PC so I don't corrupt my current system.
I will be in touch.
@.*** Cindy Cunningham Programmer Analyst
Email: @.**@.> Phone: 517-442-1981
906 James St, Adrian, MI 49221
www.adriansteel.comhttp://www.adriansteel.com/
From: Patrick Ziegler @.> Sent: Thursday, September 7, 2023 12:52 AM To: eclipse-windowbuilder/windowbuilder @.> Cc: Cindy Cunningham @.>; State change @.> Subject: [EXTERNAL] Re: [eclipse-windowbuilder/windowbuilder] WindowBuilder was not able to show the GUI (Issue #533)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
Hi Cindy. Sorry, I lost track of this problem. But the general problem is that I just can't reproduce this exception, so I have a really hard time coming up with a solution...
Perhaps let's try to reproduce this in a more controlled environment. I think you're using the Eclipse IDE. Can you instead try to download and install the Eclipse SDK? https://download.eclipse.org/eclipse/downloads/drops4/R-4.28-202306050440/
Just download & unpack the zip archive for your operating system. [Image removed by sender. image]https://user-images.githubusercontent.com/70652978/266206308-c7d8bb8c-be4c-41bd-adf3-b74f008cf069.png
Then install the latest WindowBuilder milestone https://download.eclipse.org/windowbuilder/updates/milestone/S202309051601/
Then open this test widget:
package com.adriansteel.test;
import java.awt.GraphicsConfiguration;
import java.awt.HeadlessException;
import javax.swing.JPanel;
import java.awt.BorderLayout;
import java.awt.GridBagLayout;
import javax.swing.JTabbedPane;
import javax.swing.JTextField;
import javax.swing.border.EmptyBorder;
import javax.swing.JButton;
import javax.swing.JFrame;
import java.awt.GridBagConstraints;
import java.awt.FlowLayout;
import javax.swing.JLabel;
import java.awt.Insets;
public class MyTestApp extends JFrame {
private JPanel pnlNorth;
private JTabbedPane tabbedPane;
private JTextField textField;
private JPanel pnlEast;
private JPanel pnlSouth;
private JButton btnNewButton;
private JLabel lblNewLabel;
private JLabel lblNewLabel_1;
public MyTestApp() throws HeadlessException {
getContentPane().add(getPnlNorth(), BorderLayout.NORTH);
getContentPane().add(getTabbedPane(), BorderLayout.CENTER);
getContentPane().add(getPnlEast(), BorderLayout.EAST);
getContentPane().add(getPnlSouth(), BorderLayout.SOUTH);
// TODO Auto-generated constructor stub
}
public MyTestApp(GraphicsConfiguration arg0) {
super(arg0);
// TODO Auto-generated constructor stub
}
public MyTestApp(String arg0) throws HeadlessException {
super(arg0);
// TODO Auto-generated constructor stub
}
public MyTestApp(String arg0, GraphicsConfiguration arg1) {
super(arg0, arg1);
// TODO Auto-generated constructor stub
}
public static void main(String[] args) {
// TODO Auto-generated method stub
}
private JPanel getPnlNorth() {
if (pnlNorth == null) {
pnlNorth = new JPanel();
pnlNorth.setLayout(new BorderLayout(0, 0));
pnlNorth.add(getTextField(), BorderLayout.NORTH);
}
return pnlNorth;
}
private JTabbedPane getTabbedPane() {
if (tabbedPane == null) {
tabbedPane = new JTabbedPane(JTabbedPane.TOP);
}
return tabbedPane;
}
private JTextField getTextField() {
if (textField == null) {
textField = new JTextField();
}
return textField;
}
private JPanel getPnlEast() {
if (pnlEast == null) {
pnlEast = new JPanel();
GridBagLayout gbl_pnlEast = new GridBagLayout();
gbl_pnlEast.columnWidths = new int[] {0, 0};
gbl_pnlEast.rowHeights = new int[] {0, 0, 0};
gbl_pnlEast.columnWeights = new double[]{0.0, Double.MIN_VALUE};
gbl_pnlEast.rowWeights = new double[]{0.0, 0.0, Double.MIN_VALUE};
pnlEast.setLayout(gbl_pnlEast);
GridBagConstraints gbc_lblNewLabel = new GridBagConstraints();
gbc_lblNewLabel.insets = new Insets(0, 0, 5, 0);
gbc_lblNewLabel.gridx = 0;
gbc_lblNewLabel.gridy = 0;
pnlEast.add(getLblNewLabel(), gbc_lblNewLabel);
GridBagConstraints gbc_lblNewLabel_1 = new GridBagConstraints();
gbc_lblNewLabel_1.gridx = 0;
gbc_lblNewLabel_1.gridy = 1;
pnlEast.add(getLblNewLabel_1(), gbc_lblNewLabel_1);
}
return pnlEast;
}
private JPanel getPnlSouth() {
if (pnlSouth == null) {
pnlSouth = new JPanel();
pnlSouth.add(getBtnNewButton());
}
return pnlSouth;
}
private JButton getBtnNewButton() {
if (btnNewButton == null) {
btnNewButton = new JButton("New button");
}
return btnNewButton;
}
private JLabel getLblNewLabel() {
if (lblNewLabel == null) {
lblNewLabel = new JLabel("New label");
}
return lblNewLabel;
}
private JLabel getLblNewLabel_1() {
if (lblNewLabel_1 == null) {
lblNewLabel_1 = new JLabel("New label");
}
return lblNewLabel_1;
}
}
If you open this in design page and try to delete "New label", does the error still show up?
- Reply to this email directly, view it on GitHubhttps://github.com/eclipse-windowbuilder/windowbuilder/issues/533#issuecomment-1709472492, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAQLGWDJWDKMXJYWSXJLMQTXZFHHFANCNFSM6AAAAAA3J6LRMY. You are receiving this because you modified the open/close state.Message ID: @.***>
I downloaded but could not install the JDK you listed. I am getting "Version 1.8.0_144 of the JVM is not suitable for this product. Version 17 or greater is required."
You can also install the Eclipse SDK via the installer. This should then automatically install the required JDK as well: https://www.eclipse.org/downloads/packages/installer
Just scroll down until you get to the SDK entry and the installer should do the rest.
I tried to install Eclipse on my laptop just to see if a clean install has the same issues as my regular PC and I got this. @.***
Then I installed Eclipse IDE and JDK 1.8 and JKD 17 because I need to build with 1.8.0 Changed my eclipse.ini file
Now my Eclipse opens but when I try to Open With WindowBuilder Editor I do not get a Design tab.
I am getting very frustrated and am ready to just go back to Neon.
Is there any help that you can offer?
@.*** Cindy Cunningham Programmer Analyst
Email: @.**@.> Phone: 517-442-1981
906 James St, Adrian, MI 49221
www.adriansteel.comhttp://www.adriansteel.com/
From: Patrick Ziegler @.> Sent: Friday, September 8, 2023 1:01 AM To: eclipse-windowbuilder/windowbuilder @.> Cc: Cindy Cunningham @.>; State change @.> Subject: [EXTERNAL] Re: [eclipse-windowbuilder/windowbuilder] WindowBuilder was not able to show the GUI (Issue #533)
You don't often get email from @.**@.>. Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
I downloaded but could not install the JDK you listed. I am getting "Version 1.8.0_144 of the JVM is not suitable for this product. Version 17 or greater is required."
You can also install the Eclipse SDK via the installer. This should then automatically install the required JDK as well: https://www.eclipse.org/downloads/packages/installer
Just scroll down until you get to the SDK entry and the installer should do the rest. [image]https://user-images.githubusercontent.com/70652978/266506399-f25f316e-8fa4-42c5-a292-af4f60db828a.png
- Reply to this email directly, view it on GitHubhttps://github.com/eclipse-windowbuilder/windowbuilder/issues/533#issuecomment-1711076679, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAQLGWCUPDDKZR4NCGIUNN3XZKQ65ANCNFSM6AAAAAA3J6LRMY. You are receiving this because you modified the open/close state.Message ID: @.**@.>>
Hold on... you're using an actual Java 8?
That explains a lot. And if I switch to such an old Java version, I get exactly the same error... Internally, we're using the native Eclipse compiler to process the Java code, which is build (and tested) against Java 17. My guess is that this is an incompatibility that was introduced at some point during their development cycle. And given that this doesn't show up with newer versions, not something that is likely to get fixed.
because I need to build with 1.8.0
I think it's just not possible anymore to run recent versions WindowBuilder with Java 8, meaning you need to migrate to a newer Java version, if you want to use it.
If you need to run the code with Java 8, then you could instead set the compiler compliance of your Eclipse project to 1.8. The resulting code should then still be executable with Java 8, even though it was compiled with a newer version.
I did a clean install with Java 17 on a completely different computer. Installed WindowBuilder and can not get the Design tab. Even without attempting to set my compiler to Java 8.
Is Neon still available if we want to revert back?
@.*** Cindy Cunningham Programmer Analyst
Email: @.**@.> Phone: 517-442-1981
906 James St, Adrian, MI 49221
www.adriansteel.comhttp://www.adriansteel.com/
From: Patrick Ziegler @.> Sent: Tuesday, October 10, 2023 3:01 PM To: eclipse-windowbuilder/windowbuilder @.> Cc: Cindy Cunningham @.>; State change @.> Subject: [EXTERNAL] Re: [eclipse-windowbuilder/windowbuilder] WindowBuilder was not able to show the GUI (Issue #533)
You don't often get email from @.**@.>. Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
Hold on... you're using an actual Java 8?
That explains a lot. And if I switch to such an old Java version, I get exactly the same error... Internally, we're using the native Eclipse compiler to process the Java code, which is build (and tested) against Java 17. My guess is that this is an incompatibility that was introduced at some point during their development cycle. And given that this doesn't show up with newer versions, not something that is likely to get fixed.
because I need to build with 1.8.0
I think it's just not possible anymore to run recent versions WindowBuilder with Java 8, meaning you need to migrate to a newer Java version, if you want to use it.
If you need to run the code with Java 8, then you could instead set the compiler compliance of your Eclipse project to 1.8. The resulting code should then still be executable with Java 8, even though it was compiled with a newer version.
- Reply to this email directly, view it on GitHubhttps://github.com/eclipse-windowbuilder/windowbuilder/issues/533#issuecomment-1756059891, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAQLGWHUKZM5WRCJO3J4BSTX6WLOXAVCNFSM6AAAAAA3J6LRM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJWGA2TSOBZGE. You are receiving this because you modified the open/close state.Message ID: @.**@.>>
Installed WindowBuilder and can not get the Design tab. Even without attempting to set my compiler to Java 8.
What's the error you got? If you've attached a screenshot to previous your email, then it hasn't been uploaded to GitHub.
Is Neon still available if we want to revert back?
The release will always be available for the foreseeable future: https://www.eclipse.org/downloads/packages/release/Neon/3 There is just no guarantee that it'll be compatible with the latest WindowBuilder, though.
The screen shot said something like... A Java Runtime Environment (JRE) or Java Development Kit (JDK) Must be available in order to run Eclipse..... so I installed the JDK 17.
But that was just to launch Eclipse.
According to what you said all of the newer versions of Eclipse cannot be used to build over Java 8 so I guess we are stuck with reverting back to Neon.
I appreciate your response. Just wish we would have know that earlier or I would have never upgraded.
We are going to be going thru some process changes here so hopefully we will get away from Java 8. Unfortunately I don't think that will be nearly soon enough.
Thanks again for your prompt feedback.
Cindy
@.*** Cindy Cunningham Programmer Analyst
Email: @.**@.> Phone: 517-442-1981
906 James St, Adrian, MI 49221
www.adriansteel.comhttp://www.adriansteel.com/
From: Patrick Ziegler @.> Sent: Tuesday, October 10, 2023 3:16 PM To: eclipse-windowbuilder/windowbuilder @.> Cc: Cindy Cunningham @.>; State change @.> Subject: [EXTERNAL] Re: [eclipse-windowbuilder/windowbuilder] WindowBuilder was not able to show the GUI (Issue #533)
You don't often get email from @.**@.>. Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
Installed WindowBuilder and can not get the Design tab. Even without attempting to set my compiler to Java 8.
What's the error you got? If you've attached a screenshot to previous your email, then it hasn't been uploaded to GitHub.
Is Neon still available if we want to revert back?
The release will always be available for the foreseeable future: https://www.eclipse.org/downloads/packages/release/Neon/3 There is just no guarantee that it'll be compatible with the latest WindowBuilder, though.
- Reply to this email directly, view it on GitHubhttps://github.com/eclipse-windowbuilder/windowbuilder/issues/533#issuecomment-1756079494, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAQLGWB257JGT5EAN3HKH4LX6WNG7AVCNFSM6AAAAAA3J6LRM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJWGA3TSNBZGQ. You are receiving this because you modified the open/close state.Message ID: @.**@.>>
I'm closing this as "Not Planned". From what I can tell, this problem exclusively shows up with Java 8, but not with any newer JDK. Given that Java 8 is slowly phased out, I don't think it's worth spending much time trying to figure out what exactly goes wrong here, especially because I believe it's a combination between WindowBuilder and JDT.
I upgraded from Eclipse Neon which was not having any problems to Eclipse 2023-06. Since then, I have issues when using GridBagLayout. Every time I use the Pallet to drop a component onto my JPanel. If I try to change a label text or rename a component I get errors.
I added a new label and tried to set the text and got this error. Internal Error WindowBuilder encountered unexpected internal error. This could be caused by a WindowBuilder bug or by a misconfiguration issue, conflict, partialupdate, etc. org.eclipse.wb.internal.core.utils.check.AssertionFailedException: assertion failed
If I try to Delete Contents of a row or Delete Row I get this error Internal Error WindowBuilder encountered unexpected internal error. This could be caused by a WindowBuilder bug or by a misconfiguration issue, conflict, partialupdate, etc. java.lang.IndexOutOfBoundsException: Index: 1, Length: 0
I have tried to update WindowBuilder and check all plugins and settings I can think of.
Can anyone offer any suggestions on resolving this issue? Eclipse_WindowBuilder_bugs.txt