Thomas,
Thank you, as always, for your thoughtful reply. I wonder how you get any
real work done with your dedication to this forum. I suspect you get a bit
less sleep than me.
The flush technique works fine. I even managed to craft a little editor
visitor that passes a flush command to
I found the solution. I was using an editor decorator to wrap the
number validating editor. In this case it appears that you must forward
the setDelegate from the editor decorator to its sub-editor as in:
@Override
public void setDelegate(EditorDelegateT delegate) {
if (editor
Actually, that only fixed part of my problem: the fact that the editor was
not reporting errors at all (because it was not getting a delegate). I
still do not have a good solution to the original question.
Sorry about the confusion.
On Monday, October 8, 2012 7:40:29 AM UTC-5, RickL wrote:
There is a workaround, but it is not very elegant. You can do a
driver.flush() in a change handler for the field you want to validate
on-the-fly which, of course, re-validates (i.e. calls getValue()) on all
fields. That seems to me a bit like swatting a fly with a sledgehammer.
It would seem
On Monday, October 8, 2012 3:56:57 PM UTC+2, RickL wrote:
There is a workaround, but it is not very elegant. You can do a
driver.flush() in a change handler for the field you want to validate
on-the-fly which, of course, re-validates (i.e. calls getValue()) on all
fields. That seems to
