When adding a mouseOver/mouseOut handler to a StatefulCanvas via SmartGWT 3.1, the code in Canvas.java (setupMouseOverEvent, setupMouseOutEvent) effectively replaces the standard implementation of mouseOver/mouseOut in StatefulCanvas.js.
As far as I can see, there is no possibility to trigger the standard behavior (rollover effects) from within the GWT event handler anymore.
This seems to me like a rather unique and surprising implementation choice here. Normally, SmartGWT event handlers act nicely together with the SmartClient implementations, for example, drag and drop events: I can add my custom implementation and still decide whether the standard behavior should be executed or not (by invoking cancel() on the event).
I find it somewhat odd and inconsistent that I must reimplement the standard behavior manually for mouseOver/mouseOut when adding the corresponding SmartGWT handlers.
As far as I can see, there is no possibility to trigger the standard behavior (rollover effects) from within the GWT event handler anymore.
This seems to me like a rather unique and surprising implementation choice here. Normally, SmartGWT event handlers act nicely together with the SmartClient implementations, for example, drag and drop events: I can add my custom implementation and still decide whether the standard behavior should be executed or not (by invoking cancel() on the event).
I find it somewhat odd and inconsistent that I must reimplement the standard behavior manually for mouseOver/mouseOut when adding the corresponding SmartGWT handlers.
Comment