Thanks Colin, HasEditorErrors<T> makes sense. Just to recap this approach:
Every editor knows the primitive fields it's editing. If the editor implements HadEditorErrors.showErrors(), it can simply compare primitiveField.asEditor() with error.getEditor() and highlight the erroneous primitiveField. As an alternative, a wrapper around a primitive field, like ValueBoxEditorDecorator<T>, can deal with the highlighting. Thanks again! -- 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.
