-
13 Dec 2012 5:44 AM #11
We are also having the similar issue. Can any one help us, in which version of GXT it got resolved.
-
13 Dec 2012 6:18 AM #12
Balakishan - I was never able to reproduce it after the actual 3.0.0 release, and definitly not in 3.0.1, the current non-support-subscriber release. If you are using an earlier version than those, consider upgrading, or defer the call to flush() using the scheduler class - that's how we got around in in very early releases before we resolved the button focus issue.
If you can provide the specific details of your case - what version of GXT, what browser, and the circumstances around calling flush() - we can probably be more helpful.
-
3 May 2013 1:14 AM #13
I faced the same problem and I found that the demo code calls flush() method twice and this solve the problem!
save.addSelectHandler(new SelectHandler() {
@Override
public void onSelect(SelectEvent event) {
driver.flush();
stock = driver.flush();
if (driver.hasErrors()) {
new MessageBox("Please correct the errors before saving.").show();
return;
}
updateDisplay();
stockStore.update(stock);
}
});
-
3 May 2013 8:29 AM #14
Whoops, that should have been removed - we added that back in GWT 2.3 or 2.2 to solve a bug in GWT itself. If memory serves, it was related to checking for errors.
Which version of GWT and GXT are you using? I think this is working with GWT 2.4.0 and GXT 3.0.1, and I'll remove the extra driver.flush() from our examples to avoid later confusion.
Thank you for reporting this bug. We will make it our priority to review this report.


Reply With Quote