Re: EditorDriver.setViolations in 2.3 release branch doesn't work as expected

2011-06-05 Thread veenatic
Hi, I stumbled upon this issue as well with 2.3 release. Is there any workaround or we have to wait to get the fix from google? Thanks -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://group

Re: EditorDriver.setViolations in 2.3 release branch doesn't work as expected

2011-03-16 Thread Marcin Misiewicz
I post the new issue regarding to editorDriver.setViolations http://code.google.com/p/google-web-toolkit/issues/detail?id=6153 -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googleg

Re: EditorDriver.setViolations in 2.3 release branch doesn't work as expected

2011-03-15 Thread misq...@gmail.com
Now I get it. I have missed ZipPlusCodeBox. Thanks again. Although I still got the problem with editorDriver.setViolations in my example and in DynaTableRf. 15-03-2011 20:13 użytkownik "Thomas Broyer" napisał: -- You received this message because you are subscribed to the Google Groups "Google

Re: EditorDriver.setViolations in 2.3 release branch doesn't work as expected

2011-03-15 Thread Thomas Broyer
On Tuesday, March 15, 2011 7:09:08 PM UTC+1, Marcin Misiewicz wrote: > > Also, I'm confused, what kind of errors are recorded by the editorDriver > during flushing. > In DynaTableRF checking for errors after flush results in one error related > to the zipCode field (so suprisingly it looks lik

EditorDriver.setViolations in 2.3 release branch doesn't work as expected

2011-03-15 Thread Marcin Misiewicz
Hi Lately I have a problem with calling isChanged on RequestContext here is the link to discussion on that topic https://groups.google.com/d/topic/google-web-toolkit/HznAkg94WUc/discussion Thomas has suggested that my problems can be solved by using editorDriver.isDirty introduced in gwt 2.3.