I made similar experiences, in GWT 2.8 the SDM cache is sometimes corrupt
and even a restart of SDM won't bring it back alive. Only solution I found
was cleaning temporary files.
In GWT 2.7 there was sometimes the need to restart SDM, but never the need
to clean the temporary files.
On Friday, July 22, 2016 at 9:08:57 AM UTC+2, Steve Andrews wrote:
>
> I've now got this to work. I cleaned my SDM cache :-)
>
> It only works with the generateJsInteropExports flag set though.
>
>
> On Thursday, 21 July 2016 15:34:19 UTC+1, Steve Andrews wrote:
>>
>> I've been trying out the new Elemental and have been having trouble with
>> EventListener. I'm on the latest GWT Snapshot (2.8.0-20160721.060317-297).
>> It seems that the EventListener gets compiled out unless I use the
>> Node.AddEventListenerListenerCallback function. Example:
>>
>> searchButton.addEventListener("click",e -> doSearch());
>>
>> This gets compiled out and never gets called.
>>
>> searchButton.addEventListener("click", e-> {doSearch();return true;});
>>
>> This works using the AddEventListenerListenerCallback function.
>>
>> I've tried compiling with and without the -generateJsInteropExports flag
>> and get the same result. I was using an earlier GWT snapshot version (end
>> of June) until a few days ago and didn't get the problem with that version.
>>
>> Any ideas or is this a bug?
>> Thanks
>> Steve
>>
>
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/4dac046e-1761-4764-8543-92addc49a4c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
