This is the error: [ERROR] Uncaught exception escaped java.lang.NullPointerException: null at com.google.gwt.dev.shell.ie.ModuleSpaceIE6.invokeNative(ModuleSpaceIE6.java :377) at com.google.gwt.dev.shell.ie.ModuleSpaceIE6.invokeNativeVoid(ModuleSpaceIE6. java:283) at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeVoid(JavaScriptHost.jav a:127) at org.gwtwidgets.client.wrap.Effect.move(Effect.java:235)
but as I say, when I compile to JS to use Firebug and see what it's all about, everything works like a champ.
> This is the error: > [ERROR] Uncaught exception escaped > java.lang.NullPointerException: null > at > com.google.gwt.dev.shell.ie.ModuleSpaceIE6.invokeNative(ModuleSpaceIE6.java :377) > at > com.google.gwt.dev.shell.ie.ModuleSpaceIE6.invokeNativeVoid(ModuleSpaceIE6. java:283) > at > com.google.gwt.dev.shell.JavaScriptHost.invokeNativeVoid(JavaScriptHost.jav a:127) > at org.gwtwidgets.client.wrap.Effect.move(Effect.java:235)
> but as I say, when I compile to JS to use Firebug and see what it's all > about, everything works like a champ.
Hi jdwyah,
I'm running into the same problem with opacity, and see this exception in hosted mode only:
[WARN] Exception thrown into JavaScript java.lang.NullPointerException: null at com.google.gwt.dev.shell.ie.ModuleSpaceIE6.invokeNative(ModuleSpaceIE6.java :377) at com.google.gwt.dev.shell.ie.ModuleSpaceIE6.invokeNativeVoid(ModuleSpaceIE6. java:283) at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeVoid(JavaScriptHost.jav a:127) at org.gwtwidgets.client.wrap.Effect.opacity(Effect.java:288) at org.gwtwidgets.client.wrap.Effect.opacity(Effect.java:285)
I looked at the org.gwtwidgets.client.wrap.Effect.opacity method, and it looks like: --------------- private native static void opacity (Element element, JavaScriptObject opts) /*-{ $wnd._nativeExtensions = false; new $wnd.Effect.Opacity(element, opts); }-*/; ---------------
So, it looks like it's failing on the native call. I load the effects.js and prototype.js files into the HTML file that I'm running in hosted mode, but perhaps the hosted browser isn't seeing those files.
I'm using Scriptaculous 1.6.5 and gwt-widgets 0.1.3. GWT version 1.2.22. I have IE 6 running on my computer and don't see any javascript errors there (when I compile to javascript).
Did you ever get this problem solved?
I searched on the bug list and didn't see anything.
Solution of the moment is just to wrap the call. Since it works fine in FF & IE when it's compiled to JS and only fails in hosted development mode I'm just writing a "compatibility mode" for my calls which doesn't use the fancy EffectOptions.
public static void doMove(Widget w, int x, int y,int duration){
if(GWT.isScript()){ Effects.moveBy(w,new EffectOptions( duration, x, y etc); }else{ Effects.moveBy(w,x,y); }
Thanks. This won't really work for me, as I am trying to debug some of the behavior of effect queueing.
I investigated further and it appears that the buildOptions method in the org.gwtwidgets/client/wrap/Effect.java file is to blame. The javascript object that is created there is not available in the Opacity method in scriptaculous/effects.js (again, only in hosted mode). I have some ideas on how to fix this (change the gwt-widget library, create my own options JavaScript object and try with that), but am not sure if I'll have time to investigate them.
I will appreciate it if you guys can show me some examples of Scriptaculous scale Effect and sample code. I have so far been unable to scale successfully although other effects like fade and squish work fine. I am trying to scale a panel with several image widgets on it.
mooreds wrote: > Thanks. This won't really work for me, as I am trying to debug some of > the behavior of effect queueing.
> I investigated further and it appears that the buildOptions method in > the org.gwtwidgets/client/wrap/Effect.java file is to blame. The > javascript object that is created there is not available in the Opacity > method in scriptaculous/effects.js (again, only in hosted mode). I > have some ideas on how to fix this (change the gwt-widget library, > create my own options JavaScript object and try with that), but am not > sure if I'll have time to investigate them.
I found something weird in GWT widgets library. It's just as if options didnt worked... I suggest you just to try to put a duration option that is not ambigous : lets say 10 seconds, or set a boolean option to non-default value. You'll see, it didnt work.
The mistake is in the way EffectOption are builded.
I suggest you to just re-wrap the library and making the above modifications... That worked fine for me. Actually, i completely re- write this wrapping, adding more usefull classes to manage callback and effects transitions. Plus, i'm curently working on queue and parallel.
I think there is also a bug in the GWT hosting mode: it seems it fails if one of the argument passed to a JSNI method as a '.' inside. As and the duration is a double, it almost met this condition.
Jeff
On Mar 19, 2:22 pm, "seb2nim" <seb.le...@gmail.com> wrote:
> I found something weird in GWT widgets library. It's just as if > options didnt worked... I suggest you just to try to put a duration > option that is not ambigous : lets say 10 seconds, or set a boolean > option to non-default value. You'll see, it didnt work.
> The mistake is in the way EffectOption are builded.
> I suggest you to just re-wrap the library and making the above > modifications... That worked fine for me. Actually, i completely re- > write this wrapping, adding more usefull classes to manage callback > and effects transitions. Plus, i'm curently working on queue and > parallel.
> /*
> The EffectOption class revisited
> */
> public class EffectOption { > private String name;