SWT Designer allows you to create the views, editors, perspectives, pref pages, composites, etc. that comprise Eclipse SWT & RCP applications and plug-ins.
Moderators: Konstantin.Scheglov, gnebling, Alexander.Mitin, jwren, Eric Clayberg
by redlaber » Tue Sep 21, 2010 1:35 pm
I installed the Google WindowBuilder Pro on Eclipse 3.6 in Ubuntu 10.04. I created Application Window in my project and its work fine. But when i try to switch to the "Design" tab i get the error:
org.eclipse.swt.SWTError: No more handlesHere is a stacktrace:
- Code: Select all
org.eclipse.swt.SWTError: No more handles
at org.eclipse.swt.SWT.error(SWT.java:4109)
at org.eclipse.swt.SWT.error(SWT.java:3998)
at org.eclipse.swt.SWT.error(SWT.java:3969)
at org.eclipse.swt.widgets.Composite.createHandle(Composite.java:275)
at org.eclipse.swt.widgets.Shell.createHandle(Shell.java:679)
at org.eclipse.swt.widgets.Widget.createWidget(Widget.java:412)
at org.eclipse.swt.widgets.Control.createWidget(Control.java:543)
at org.eclipse.swt.widgets.Scrollable.createWidget(Scrollable.java:152)
at org.eclipse.swt.widgets.Decorations.createWidget(Decorations.java:240)
at org.eclipse.swt.widgets.Shell.<init>(Shell.java:280)
at org.eclipse.swt.widgets.Shell.<init>(Shell.java:253)
at org.eclipse.swt.widgets.Shell.<init>(Shell.java:204)
at org.eclipse.swt.widgets.Shell.<init>(Shell.java:140)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at com.instantiations.designer.core.eval.evaluators.InvocationEvaluator.evaluate(InvocationEvaluator.java:251)
I try different solutions of this problem, but no one helps
Pleas help me!
Last edited by
redlaber on Tue Sep 21, 2010 2:31 pm, edited 1 time in total.
-
redlaber
-
- Posts: 10
- Joined: Tue Sep 21, 2010 1:27 pm
-
by Eric Clayberg » Tue Sep 21, 2010 2:13 pm
That typically means that Eclipse (or the OS) was already very low on memory before you even accessed WB.
What happens if you reboot and restart Eclipse? Can you provide a reproducible test case?
-
Eric Clayberg
- Moderator
-
- Posts: 4503
- Joined: Tue Sep 30, 2003 6:39 am
- Location: Boston, MA USA
-
by redlaber » Tue Sep 21, 2010 2:23 pm
Restarting Eclipse and OS didn`t helps. Memory usege is low. Eclipse use 200 MB of my 3GB RAM.
-
redlaber
-
- Posts: 10
- Joined: Tue Sep 21, 2010 1:27 pm
-
by redlaber » Tue Sep 21, 2010 2:29 pm
I tried:
- Creating new workspace
- Installing older version of SWT
- elcipse -clean
- Starting Eclipse with xulrunner support
The problem arise every time i open the "Design" tab. I cant use Designer
-
redlaber
-
- Posts: 10
- Joined: Tue Sep 21, 2010 1:27 pm
-
by Alexander.Mitin » Wed Sep 22, 2010 12:27 am
Is your OS 32-bit or 64-bit?
Alexander Mitin
-
Alexander.Mitin
- Moderator
-
- Posts: 155
- Joined: Fri Jan 19, 2007 3:57 am
by Alexander.Mitin » Wed Sep 22, 2010 12:37 am
Additionally, we need see your Eclipse log file (<workspace>/.metadata/.log) as well as reproducible test case.
Does this happen on every UI which you try to open or only certain one?
Alexander Mitin
-
Alexander.Mitin
- Moderator
-
- Posts: 155
- Joined: Fri Jan 19, 2007 3:57 am
by redlaber » Wed Sep 22, 2010 9:44 am
I attached the log file. It begins from eclipse start and ends by the error. And I apologize for not perfect knowledge of English, but what means "reproducible test case"?
- Attachments
-
eclipse_log.txt- (14.39 KiB) Downloaded 29 times
-
redlaber
-
- Posts: 10
- Joined: Tue Sep 21, 2010 1:27 pm
-
by redlaber » Wed Sep 22, 2010 9:50 am
O! And its happend on every SWT UI!
-
redlaber
-
- Posts: 10
- Joined: Tue Sep 21, 2010 1:27 pm
-
by Eric Clayberg » Wed Sep 22, 2010 3:13 pm
If this happening on any SWT UI, something must be very unusual about your Eclipse config.
Please send us a screen shot of your "Help > About > Installation Details > Installed Software" page as well as a copy of your complete "Help > About > Installation Details > Configuration".
-
Eric Clayberg
- Moderator
-
- Posts: 4503
- Joined: Tue Sep 30, 2003 6:39 am
- Location: Boston, MA USA
-
-
redlaber
-
- Posts: 10
- Joined: Tue Sep 21, 2010 1:27 pm
-
by Alexander.Mitin » Thu Sep 23, 2010 1:31 pm
What if to try with fresh clean Eclipse with only the SWT Designer (not the entire WindowBuilder) installed? Please try with
Eclipse Classic.
"No more handles" SWT error under Linux usually means that something went wrong while creating underlying GTK resources, ex., g_object_new() returned NULL.
We cannot reproduce this on our end.
Alexander Mitin
-
Alexander.Mitin
- Moderator
-
- Posts: 155
- Joined: Fri Jan 19, 2007 3:57 am
by redlaber » Thu Sep 23, 2010 1:33 pm
Alexander.Mitin wrote:What if to try with fresh clean Eclipse with only the SWT Designer (not the entire WindowBuilder) installed? Please try with
Eclipse Classic.
"No more handles" SWT error under Linux usually means that something went wrong while creating underlying GTK resources, ex., g_object_new() returned NULL.
We cannot reproduce this on our end.
Ok, I will try the clean Eclipse Classic with only SWT Designer
-
redlaber
-
- Posts: 10
- Joined: Tue Sep 21, 2010 1:27 pm
-
by Alexander.Mitin » Fri Sep 24, 2010 3:20 am
Please keep us in touch.
Alexander Mitin
-
Alexander.Mitin
- Moderator
-
- Posts: 155
- Joined: Fri Jan 19, 2007 3:57 am
by redlaber » Fri Sep 24, 2010 3:23 am
Alexander.Mitin wrote:Please keep us in touch.
I am pleased to do so. Thanks for so active help.
-
redlaber
-
- Posts: 10
- Joined: Tue Sep 21, 2010 1:27 pm
-
by redlaber » Mon Sep 27, 2010 7:56 am
So, I installed Eclipse Classic, added WB repository. I installed only SWT Designer from it. The same problem, the same error
-
redlaber
-
- Posts: 10
- Joined: Tue Sep 21, 2010 1:27 pm
-
Return to SWT Designer
Who is online
Users browsing this forum: Bing [Bot], Google [Bot] and 1 guest
