Like others, I'd like to be able to nest widgets in FlexTable within the UiBinder XML. OK, that's no go for now, but I was happy to find the workaround (link below) to define nested components elsewhere in the structure and then programmatically move them into the FlexTable. This works pretty well for me, EXCEPT for the following problem:
When I move a widget into the FlexTable via table.setWidget(row, col, Widget), any handler I attach via @UiHandler in the Java code is lost. That eliminates a nice benefit of using UiBinder. Experimenting, I've found that if I don't do widget.removeFromParent() prior to table.setWidget(), I end up with two of the widget: One at its original "dummy" location and one in my table. The "dummy" widget is still handling the event, so it appears that what's set into the table is effectively a "clone," not the original. I wouldn't mind, if the clone had a connection to the event handler. Can this be fixed or is there a workaround, please? For background on the "move widget from dummy location into the flextable" see: http://groups.google.com/group/google-web-toolkit/browse_thread/thread/8e5643639c391752/9bdab6c9e620ddcb?lnk=gst&q=Flextable+UiBinder#9bdab6c9e620ddcb, -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
