WindowBuilder not behaving in Mountain Lion [message #899288] |
Tue, 31 July 2012 11:03  |
Eclipse User |
|
|
|
Hi, I recently upgraded my Macbook to Mountain Lion and have since noticed that WindowBuilder doesn't allow me to edit properties in the property tree (Specifically clicking on a value and editing it in place). I get the following error whenever I try to edit a value:
java.lang.NullPointerException
at org.eclipse.swt.widgets.Control.invalidateVisibleRegion(Control.java:2181)
at org.eclipse.swt.widgets.Control.setFrameSize(Control.java:3802)
at org.eclipse.swt.widgets.Text.setFrameSize(Text.java:1796)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5485)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
at org.eclipse.swt.internal.cocoa.NSView.setFrame(NSView.java:267)
at org.eclipse.swt.widgets.Control.setBounds(Control.java:3536)
at org.eclipse.swt.widgets.Control.setBounds(Control.java:3571)
at org.eclipse.wb.internal.core.model.property.editor.AbstractTextPropertyEditor.setBounds(AbstractTextPropertyEditor.java:79)
at org.eclipse.wb.internal.core.model.property.table.PropertyTable.setActiveEditorBounds(PropertyTable.java:591)
at org.eclipse.wb.internal.core.model.property.table.PropertyTable.activateEditor(PropertyTable.java:536)
at org.eclipse.wb.internal.core.model.property.table.PropertyTable.handleMouseDown(PropertyTable.java:372)
at org.eclipse.wb.internal.core.model.property.table.PropertyTable.access$8(PropertyTable.java:356)
at org.eclipse.wb.internal.core.model.property.table.PropertyTable$5.mouseDown(PropertyTable.java:175)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:192)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4134)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1271)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3980)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3619)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1022)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:916)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:585)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:540)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
This was happening in Helios so I upgraded to Juno and reinstalled the WindowBuilder but I still get the same issues. I also tried creating a new Workspace and project to see if there was any issues there. Seeing as the only thing that has changed is the new OS can I assume that is the problem? Could it also be the version of SWT?
Does anyone know any workarounds for this?
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02909 seconds