[estrige]

Hello,
Recently I decided to try out Mali Developer Tools, which look very promising.

Unfortunately I have a problem with Shader Development Studio.
When trying to make SimpleTest Project (from the User Guide) while rendering the shader effect
the Shader Preview shows a triangle instead of a square shown in the Guide.
In general, it is not surprising, since the option VERTICES in Shader Attributes View has by default three
vertices:
-1.0 -1.0,0.0,1.0,
1.0 -1.0,0.0,1.0,
1.0,1.0,0.0,1.0,

The problem however is that there is no possibility to add additional vertices
(when choosing the option USER_DEFINED). You can only change the three given.
Changing the geometry in Shader Control View do not bring any effect, always showing three vertices.
Even when using a Shader Examples from Mali GPU Shader Library shaders are applied to that triangle.
The shaders themselves are working (changing color, texturing, etc).

Plugin has been tested on the following configurations:
Eclipse 3.6.2

• GeForce 9600M GT Windows 7 64bit
• GeForce GTS 250 Windows 7 32bit

All necessary OpenGL extensions are present, Emulator and Offline Shader Compiler are installed and work.

Had someone the same problem and is there a solution?
Thanks.

This post has been edited by estrige: 13 May 2011 - 12:32 AM

[rdc]

Hi estrige,

I'm trying to recreate the problem here but can't seem to reproduce this on my Windows XP platform. I find that the default geometry is in fact a plane (rather than a triangle). I don't have a Windows 7 platform handy at the moment but I don't see how this would cause an issue. Does the Eclipse error log show anything that might give us a clue (you can find it in "Window > Show View")?

In terms of adding more vertices to a geometry, this is a interesting idea and supporting arbitrary geometry is something we'd definitely like to do in the future. At the moment, selecting one of the more complex geometries should give you extra vertices to play with (once we've managed to solve your problem with selecting something other than the triangle!).

[estrige]

Yes, in general the version of windows should not play a special role here, but I was able to try the plugin
on the third computer with windows 7 already (albeit with similar characteristics that were given above)
on a clean eclipse installation. The problem is the same.

About adding additional vertices, I just wanted to add a fourth vertex to the three present, in order to
turn it into a square, but in principle, several different meshes should be sufficient for shader testing.
Speaking about the three vertices, I proceed from the fact that VERTICES variable represent 3 homogeneous vertices
(one in each row). Since I am not sure, here is a picture



In error log I found two errors related to the plugin:

The first one happened rarely apparently at the opening of a (closed) project:

Message: Unhandled event loop exception

Stack Trace:
java.lang.NullPointerException
at com.arm.mali.shaderdebugger.preview.PreviewModel.redrawPreviewImage(PreviewModel.java:542)
at com.arm.mali.shaderdebugger.preview.PreviewModel$1.run(PreviewModel.java:596)
at org.eclipse.swt.widgets.Display.runTimer(Display.java:4167)
at org.eclipse.swt.widgets.Display.messageProc(Display.java:3256)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2459)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3655)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
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:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)

As well as a "Widget is disposed" (  error.txt (6.39K)
Number of downloads: 0), when closing eclipse with an opened shader studio project.

When I try to change geometry simply nothing happens, there are no logged errors in this case.

This post has been edited by estrige: 20 May 2011 - 12:03 AM

[rdc]

Thanks for the response! I'm a bit suspicious of that NullPointerError so I will add a note about this to the internal bug tracker, and one of our developers will be able to take a look at it

[Slion]

Looks like I have the exact same problem on WinXP.
Eclipse is v3.7.0.
GPU: GeForce 8300GS
The Mali OpenGL ES 2.0 Emulator works fine when used intependently of the Shader Dev Studio.

I've tried both creating my own SimpleTest as per the PDF docs and importing ShaderExamples from the Shader Library but all I can render is single triangle.
Changing the Geometry from the Shader Control view does not help.

It's just using the hardcoded values from the Shader Attributes view. So if I edit them I can modify the render but I can't get it to use the Geometry specified by the Shader Control.

Am I simply missing something or do you have a bug with the latest Eclipse release?

[Slion]

Same issue with Eclipse 3.6.2. and 3.5.2.
I'm using OpenGL ES 2.0 Emulator v1.3.0M1
Maybe it's an issue with the Renderer Server?

This post has been edited by Slion: 01 August 2011 - 12:10 PM

[rdc]

Hi all,

I've just been trying to reproduce this issue with a Windows 7 machine, but still can't seem to make the bug appear For reference, the steps I took were:

1. Open Eclipse
2. Create a new 'General' project
3. Add a new vertex and fragment shader
4. Add a shader configuration and add the appropriate shaders. Save the shader configuration.
5. Select the 'New Effect' in the Shader Control view
6. I see that the default geometry is "PLANE"
7. Set up the attributes ('coord' to 'VERTICES') and ('camera' to 'CAMERA_MATRIX')
8. Select the built-in renderer from "Manage Renderers"
9. Render a single frame

I see at this point a coloured square. I can then select a new geometry (say, "SPHERE") and the geometry changes for me. Am I doing anything different to you? My platform is Eclipse 3.7, OpenGL ES 2.0 Emulator 1.3.0 M1, Windows 7 Professional and an NVIDIA GeForce 210.

[Projekt2501]

Hi,

I am also facing this problem, is there any workaround present to fix the geometry selection problem?

Configs:
1) Win 7 Pro 32 bit
2) Win 7 Ultimate 64 bit

Both use the most current Eclipse version.
-> using Android SDK
-> using Android Projects

Regards,

This post has been edited by Projekt2501: 17 October 2011 - 09:35 AM

[rdc]

Hi Projekt2501!

Projekt2501, on 17 October 2011 - 09:34 AM, said:

I am also facing this problem, is there any workaround present to fix the geometry selection problem?

Are you following the same procedure I outlined in my post above? I can't reproduce the issue on any platform I've tried, but I wonder if I might be doing something different to you?

[Projekt2501]

rdc, on 18 October 2011 - 11:38 PM, said:

Hi Projekt2501!



Are you following the same procedure I outlined in my post above? I can't reproduce the issue on any platform I've tried, but I wonder if I might be doing something different to you?

Yes, to the point. Tried it again a few moments ago to be sure.

The difference to your configuration seems to be the graphics card (ATI Radeon HD 5700) at first glance.

I wonder if a fresh and minimal installation of Eclipse will make a difference. Will try this next.

[Projekt2501]

With a fresh Eclipse installation (Indigo) and a fresh workspace these Exceptions can be taken from the log:

This one came up during installation:

 !ENTRY org.eclipse.jface 4 0 2011-10-19 10:43:33.422
!MESSAGE java.lang.NullPointerException
!STACK 0
java.lang.NullPointerException
	at com.arm.mali.shaderdebugger.preview.PreviewModel.setLastMRIConnection(PreviewModel.java:677)
	at com.arm.mali.visualtools.preferences.MRIPreferencePage.saveConnectionInfo(MRIPreferencePage.java:462)
	at com.arm.mali.visualtools.preferences.MRIPreferencePage.performOk(MRIPreferencePage.java:447)
	at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:964)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
	at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
	at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:944)
	at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:447)
	at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.okPressed(WorkbenchPreferenceDialog.java:171)
	at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:233)
	at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754)
	at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
	at org.eclipse.jface.window.Window.open(Window.java:801)
	at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215)
	at org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:54)
	at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)
	at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
	at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
	at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
	at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
	at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
	at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
	at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
	at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
	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:344)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1410)

This one is thrown every time Eclipse is shutting down:

 !ENTRY org.eclipse.ui.workbench 4 0 2011-10-19 10:47:56.957
!MESSAGE Widget is disposed
!STACK 0
org.eclipse.swt.SWTException: Widget is disposed
	at org.eclipse.swt.SWT.error(SWT.java:4282)
	at org.eclipse.swt.SWT.error(SWT.java:4197)
	at org.eclipse.swt.SWT.error(SWT.java:4168)
	at org.eclipse.swt.widgets.Widget.error(Widget.java:468)
	at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:340)
	at org.eclipse.swt.widgets.Label.getImage(Label.java:238)
	at com.arm.mali.shaderdebugger.preview.ShaderPreview.dispose(ShaderPreview.java:110)
	at org.eclipse.ui.internal.WorkbenchPartReference.doDisposePart(WorkbenchPartReference.java:737)
	at org.eclipse.ui.internal.ViewReference.doDisposePart(ViewReference.java:104)
	at org.eclipse.ui.internal.WorkbenchPartReference.dispose(WorkbenchPartReference.java:684)
	at org.eclipse.ui.internal.WorkbenchPage.disposePart(WorkbenchPage.java:1797)
	at org.eclipse.ui.internal.WorkbenchPage.partRemoved(WorkbenchPage.java:1789)
	at org.eclipse.ui.internal.ViewFactory.releaseView(ViewFactory.java:257)
	at org.eclipse.ui.internal.Perspective.dispose(Perspective.java:292)
	at org.eclipse.ui.internal.WorkbenchPage.dispose(WorkbenchPage.java:1868)
	at org.eclipse.ui.internal.WorkbenchWindow.closeAllPages(WorkbenchWindow.java:887)
	at org.eclipse.ui.internal.WorkbenchWindow.hardClose(WorkbenchWindow.java:1722)
	at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:730)
	at org.eclipse.ui.internal.WorkbenchWindow.access$0(WorkbenchWindow.java:715)
	at org.eclipse.ui.internal.WorkbenchWindow$5.run(WorkbenchWindow.java:860)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
	at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:858)
	at org.eclipse.jface.window.WindowManager.close(WindowManager.java:109)
	at org.eclipse.ui.internal.Workbench$18.run(Workbench.java:1109)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:1106)
	at org.eclipse.ui.internal.Workbench.access$15(Workbench.java:1035)
	at org.eclipse.ui.internal.Workbench$25.run(Workbench.java:1279)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
	at org.eclipse.ui.internal.Workbench.close(Workbench.java:1277)
	at org.eclipse.ui.internal.Workbench.close(Workbench.java:1249)
	at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:727)
	at org.eclipse.ui.internal.WorkbenchWindow.access$0(WorkbenchWindow.java:715)
	at org.eclipse.ui.internal.WorkbenchWindow$5.run(WorkbenchWindow.java:860)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
	at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:858)
	at org.eclipse.jface.window.Window.handleShellCloseEvent(Window.java:741)
	at org.eclipse.jface.window.Window$3.shellClosed(Window.java:687)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:98)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062)
	at org.eclipse.swt.widgets.Decorations.closeWidget(Decorations.java:308)
	at org.eclipse.swt.widgets.Decorations.WM_CLOSE(Decorations.java:1677)
	at org.eclipse.swt.widgets.Control.windowProc(Control.java:4530)
	at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341)
	at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1610)
	at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2061)
	at org.eclipse.swt.widgets.Display.windowProc(Display.java:4972)
	at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
	at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2526)
	at org.eclipse.swt.widgets.Shell.callWindowProc(Shell.java:498)
	at org.eclipse.swt.widgets.Control.windowProc(Control.java:4623)
	at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341)
	at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1610)
	at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2061)
	at org.eclipse.swt.widgets.Display.windowProc(Display.java:4972)
	at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
	at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2526)
	at org.eclipse.swt.widgets.Shell.callWindowProc(Shell.java:498)
	at org.eclipse.swt.widgets.Control.windowProc(Control.java:4623)
	at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341)
	at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1610)
	at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2061)
	at org.eclipse.swt.widgets.Display.windowProc(Display.java:4972)
	at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
	at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2531)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3752)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
	at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
	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:344)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1410)

Maybe it helps to find a solution to the problem.

[Projekt2501]

The fact that I did a fresh install and it still does not work is quite odd. For me it looks like an issue indirectly related to Eclipse may be at hand. Like Java installation JRE/SDK maybe.
@rdc: Here some questions that might help to get the issue pinned.

1) Where did you install the ARM files? Default folder?
2) Any special changes to the system? I am thinking of tinkering with the PATH variable and permissions maybe.

This post has been edited by Projekt2501: 19 October 2011 - 09:04 AM

[rdc]

Thanks, that's helpful!

I don't feel that the two exceptions you mentioned are related to this problem; the first looks like an accidental call to set a previous renderer connection when none exists, and the second is someone trying to dispose an SWT widget that's already been disposed (both are bugs, and I've logged them in our bug tracker).

My installation of Eclipse was also a fresh 3.7, running on Java 6. I haven't tried it on Java 7 yet. Maybe you're on to something there. I'll try to install Java 7 and try to reproduce it.

In answer to your questions; I installed everything to the default locations and haven't made any changes to the PATH etc that weren't made by the installers themselves (i.e. adding the OpenGL ES 2.0 Emulator to the PATH).

[Projekt2501]

Might be helpful.

java -version yields:

java version "1.6.0_29"
Java™ SE Runtime Environment (build 1.6.0_29-b11)
Java HotSpot™ Client VM (build 20.4-b02, mixed mode, sharing)

If you have additional ideas or want me to try out a bugfix/workaround I will help out.

This post has been edited by Projekt2501: 20 October 2011 - 09:58 AM

[rdc]

Hmm, that's frustrating—I was hoping that it would be an issue with Java 7, but evidently the problem exists with Java 6, too. I'll need to do some more investigation.

[isogen74]

One thought - when running are you running as administrator or as an unpriviledged user? Windows 7 is a lot more picky about what it lets a non-admin write to specific locations.

[Projekt2501]

isogen74, on 24 October 2011 - 11:34 AM, said:

One thought - when running are you running as administrator or as an unpriviledged user? Windows 7 is a lot more picky about what it lets a non-admin write to specific locations.

Already tried that, no success :/

[aharali]

Same here. Windows 7 and Eclipse Juno.

[DrNoes]

Hi there,

just wanted to bump this topic... i have the same problem on
Win 7 64bit
JDK7_17
Eclipse Juno
latest Android SDK (and projects)

Is there any solution yet?

Best Regards

DrNoes



EDIT: This Error message appears in the logs, when I try to save chages in the shader control:


java.lang.ClassCastException: org.eclipse.ui.editors.text.TextEditor cannot be cast to com.arm.mali.shaderdevelopmentstudio.editors.ShaderStockpileEditor
at com.arm.mali.shaderdevelopmentstudio.Activator.getShaderStockpileEditor(Activator.java:660)
at com.arm.mali.shaderdevelopmentstudio.control.ShaderToolbarFactory$3.run(ShaderToolbarFactory.java:133)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1053)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:942)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
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(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
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)
at org.eclipse.equinox.launcher.Main.main(Main.java:1414)


Maybe theres a similar problem with the Dropdown-Box using deprecated (not longer used) methods to change the actual geometry ?

EDIT2:

This is the shader config... the shaders are the default vertex and fragment shaders


ShaderStockpile:
localTimeStamp: 1364053487225
shaderEffects:
ShaderEffect:
name: bounds
vertexSources:
ShaderSource:
fileName: shader\bounds.vert
fragmentSources:
ShaderSource:
fileName: shader\bounds.frag
CompilerSettings:
useCompiler: true
revisionTarget:
compilerPath: malisc
basePath:
vertexInstructionWords: 0
vertexShortestCodePath: 0
vertexLongestCodePath: 0
fragmentInstructionWords: 0
fragmentShortestCodePath: 0
fragmentLongestCodePath: 0
data: null
axis:
[0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
uniforms:
Uniform:
type: GL_FLOAT_MAT4
initialData:
data:
-[[1.0, 0.0, 0.0, 0.0],
[0.0, 1.0, 0.0, 0.0],
[0.0, 0.0, 1.0, 0.0],
[0.0, 0.0, 0.0, 1.0]]-
location: 0
name: camera
pushed: true
mapping: CAMERA_MATRIX
finalData:
data:
-[[1.0, 0.0, 0.0, 0.0],
[0.0, 1.0, 0.0, 0.0],
[0.0, 0.0, 1.0, 0.0],
[0.0, 0.0, 0.0, 1.0]]-
attributes:
Attribute:
type: GL_FLOAT_VEC4
initialData:
data:
-[-1.0, -1.0, 0.0, 1.0]
-[1.0, -1.0, 0.0, 1.0]
-[1.0, 1.0, 0.0, 1.0]-
location: 0
name: coord
pushed: true
mapping: VERTICES
backgroundColour:
[0.0, 0.0, 0.0]
orthographic: true
maxFrames: 1
geometry: PLANE
blendEnabled: true
BlendMode:
blendColour:
[0.0, 0.0, 0.5]
useEquationSeperateMode: false
useFunctionSeperateMode: false
equationMode: GL_FUNC_ADD
equationAlphaMode: GL_FUNC_ADD
blendFuncSource: GL_ONE
blendFuncDest: GL_ZERO
blendFuncSourceAlpha: GL_ONE
blendFuncDestAlpha: GL_ZERO

This post has been edited by DrNoes: 23 March 2013 - 03:46 PM

[shapkin]

Hi all,
I have had the same issue. And I think i know the root cause.
Looks like it's happens then you have non "." (point) separator in your system for float numbers. For me it was "," (coma).
So just set US locale setting.

For plugin developers: Please dont use system separator It happens inside of com.arm.mali.shaderdevelopmentstudio.callscript.Geometry. The java.util.Scanner throws java.util.InputMismatchException then trying to parse float number.
Sorry for my English.