Designer internal error: java/awt/Toolkit.setDynamicLayout()

[kleist]

Dear supporters,

When clicking the toggle "Test Designer Window" for my tiny JFrame based gadget, nothing happens. Is this a known feature?

JRE: j2sdk1.4.2_04

My log file, and contents of "e-mail tech support":
-----------------------------------------------------------------------------------

Code: Select all

!ENTRY com.swtdesigner 4 4 Aug 17, 2004 21:00:26.640
!MESSAGE Designer internal error: java/awt/Toolkit.setDynamicLayout(Z)V
!STACK 0
java.lang.NoSuchMethodError: java/awt/Toolkit.setDynamicLayout(Z)V
   at java.lang.Throwable.<init>(Throwable.java)
   at java.lang.Throwable.<init>(Throwable.java)
   at java.lang.NoSuchMethodError.<init>(NoSuchMethodError.java:56)
   at com.swtdesigner.model.swing.component.ComponentBeanInfo.show(SourceFile:801)
   at com.swtdesigner.gef.DesignerEditor.testWindow(SourceFile:754)
   at com.swtdesigner.actions.editor.TestAction.run(SourceFile:28)
   at com.swtdesigner.actions.editor.TestAction.run(SourceFile:31)
   at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
   at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
   at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java)
   at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java)
   at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java)
   at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java)
   at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java)
   at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java)
   at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java)
   at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
   at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
   at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
   at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
   at java.lang.reflect.AccessibleObject.invokeL(AccessibleObject.java:207)
   at java.lang.reflect.Method.invoke(Method.java:271)
   at org.eclipse.core.launcher.Main.basicRun(Main.java:291)
   at org.eclipse.core.launcher.Main.run(Main.java:747)
   at org.eclipse.core.launcher.Main.main(Main.java:583)


--------------------------------------------------------------------------------
Product: WindowBuilder Pro
Version: 2.0.0 compiled on 2004.06.15 for Eclipse 2.1 or WSAD 5.1.x
Platform Product: IBM WebSphere Studio Application Developer
Platform Version: 5.1.2
OS Name: Windows XP
OS Architecture: x86
OS Version: 5.1 build 2600 Service Pack 1
Priority: Standard
Log Attached: No



[Eric Clayberg]

When clicking the toggle "Test Designer Window" for my tiny JFrame based gadget, nothing happens. Is this a known feature?

This problem was fixed several weeks ago. Download and install the latest v2.0.1 build and you will be fine.

The actual problem was caused by a JDK 1.4 dependency in one Designer class which caused a problem under WSAD which runs using the 1.3 JRE by default.

[kleist]

Thanks Eric, works fine with the v2.0.1 [Stable Build] 2004.08.18 (a late night's work yesterday, I guess?). It even works with J2SE 5.0 Beta 2, which I am happy enough to be able to work with (small project, no legacy).

Normally, I tend to avoid non-GA product versions. Especially when I'm not yet a seasoned user of the product. In this case, though, I seem to have little choice. However, as a previous user of VA Assist my confidence for you is high - to say the least.

By the way: Contrary to the Visual Editor in WSAD, your product does *not* really execute the class when I "test" it. Right? And hence, java.beans.Beans.isDesignTime() is not relevant here? (You have better to check this when using VE, or the strangest things could happen... )

Cheers,
K J

[Eric Clayberg]

Normally, I tend to avoid non-GA product versions. Especially when I'm not yet a seasoned user of the product. In this case, though, I seem to have little choice. However, as a previous user of VA Assist my confidence for you is high - to say the least.

You should always feel comfortable using our most recent "Stable Build". That version will always have the benefit of the most recent bug fixes and performance improvements. I consider v2.0.1 to be a significant improvement over v2.0.0 in many respects.

By the way: Contrary to the Visual Editor in WSAD, your product does *not* really execute the class when I "test" it. Right?

Correct. Designer's test mode is simply a visual simulation so that you can quickly see how the widgets look and feel (especially when resizing the window). All of your class logic is suppressed. Note that you can always "Run" the class using the standard Eclipse "Run As > Java Application" command (this is slower).

And hence, java.beans.Beans.isDesignTime() is not relevant here?

Correct.