So you're getting "some data changed" events bubble up to the root, which flushes editors (i.e. get all the data up from all editors), to compute fields and edit again (i.e. push data down again to all editors)? That's pretty inefficient.
With that info, I think I wouldn't use EditorDriver mechanisms at all for this (which does not mean not using EditorDriver at all, just not for those " red dots"), but do it at the widget level; i.e. bind the TextBox directly to the RedDot, at the Composite level (and have RedDot totally disconnected from the EditorDriver). For the initial state, have your Composite implement ValueAwareEditor so you can compute it and initialize the RedDots in setValue. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
