To further clarify, the problem in DateBox occurs more specifically not on a date change to a new date, but when using the keyboard to blank out a date. Neither the keystroke nor the blur event on the text box fire a value change event, but the value of the date for the box *is* set to null.
On Thursday, February 16, 2012 9:28:32 AM UTC-5, Bob Lacatena wrote: > > I invariably find that GWT doesn't do exactly what I need. Too often, > however, I'm frustrated in my efforts to extend a class because too > many elements or methods are private (rather than protected) and such > private fields are not even exposed by getters and setters. > > Please go through all of your code and change "private" to > "protected". In the rare case where you really don't want someone > touching something (e.g. deprecated methods) that's fine, but think > ten times about having a private field without a getter/setter, or a > private method of any sort. Such a situation should be very, very > rare in a toolkit that's meant to be extensible, and is obviously > limited in functionality and absolutely will require that the > programmer roll up his sleeves. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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 http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
