Re: [gwt-contrib] Re: Problem with JsInterop

That is added relatively recent. And thanks for pointing the documentation issue; add a issue to review all before the final release. On Thu, Sep 1, 2016 at 10:08 PM, Arnaud TOURNIER wrote: > Thanks a lot for your answer. > > I tried the solution with defender methods earlier

Re: [gwt-contrib] Re: Problem with JsInterop

Thanks a lot for your answer. I tried the solution with defender methods earlier but it did not work, as far as i remember the compiler refused @JsOverlay defender methods on the JsFunction. The @JsFunction documentation says that : "A JsFunction interface cannot have defender methods." I will

Re: [gwt-contrib] Re: Problem with JsInterop

The limitation around @JsFunction is basically driven from the limitations of being a function. I think there was an earlier discussion in the contibutor list where we explained this in more detail. Being said that, you can handle some overloading in JsFunction interfaces via defender methods

Re: [gwt-contrib] Re: Problem with JsInterop

Oh thanks! I'll try that. Once I think we need to merge our work on those topics... Thanks! Le mar. 30 août 2016 16:06, Paul Stockley a écrit : > If you are passing Resolver into some function. You could instead > create 3 Resolver interfaces and then overload the