| Table validation
Ah, good explanation, I understand now. I hadn't thought about this, but it does seem like pretty valid and common use-cases. Given the simplicity of the code changes needed it all seems reasonable. T . . .
|
Simple Validation
» General Discussion
|
February 14, 2010 07:30
by: noelopan
|
| Table validation
Hi noelopan, > Would you please consider adding JTable support? I can't speak for Tim -- and he's the boss -- but yes, I'd definitely consider that. It seems only natural considering that we support . . .
|
Simple Validation
» General Discussion
|
February 14, 2010 07:30
by: noelopan
|
| Create/show warning messages
> If you want i will also brief you on scenario's why i require such a functionality. Yes, it would actually be interesting to hear how you're using this. If your use case is supported, it could perh . . .
|
Simple Validation
» General Discussion
|
February 09, 2010 00:02
by: hugoheden
|
| Component Decorator icon remains even if there are no errors.
This sounds like a bug, that should not be happening. Could you provide with a small test case that triggers this behavior? A lot of things have been happening with the library since last release (Val . . .
|
Simple Validation
» General Discussion
|
February 19, 2010 18:54
by: Tim Boudreau
|
| The dev-hh-2 branch
During the weekend I thought I'd work on the code a bit as discussed in this forum thread. Tim, how would that fit with what you're currently doing? o) Things I thought I would work on: * Finish t . . .
|
Simple Validation
» General Discussion
|
January 29, 2010 09:53
by: hugoheden
|
| The dev-hh-2 branch
Yes, I'm slightly concerned with ValidationGroup being non-final. To me this looks like a typical case of mixing API and SPI, doesn't it? The type() solution sounds like it could work.
|
Simple Validation
» General Discussion
|
January 29, 2010 09:53
by: hugoheden
|
| The dev-hh-2 branch
> I notice we have ValidationItem.performValidation(), which is public final. Then there is ValidationListener, > a subclass of ValidationItem, which has protected final triggerValidation() that just . . .
|
Simple Validation
» General Discussion
|
January 29, 2010 09:53
by: hugoheden
|
| The dev-hh-2 branch
It will disable the ValidationUI:s of the added child group . The ValidationUI of the parent group will still be enabled. I figured the parent is the one that typically manages an OK button or Next bu . . .
|
Simple Validation
» General Discussion
|
January 29, 2010 09:53
by: hugoheden
|
| The dev-hh-2 branch
All the above is still supported.. hrm, and if I'm wrong it should be pretty easy to rectify -- the functionality is pretty much there, it's just been removed from the API. > Not sure if I understand . . .
|
Simple Validation
» General Discussion
|
January 29, 2010 09:53
by: hugoheden
|
| The dev-hh-2 branch
One other thing - I think for ValidationUI, setProblem(Problem) and clearProblems() is probably clearer. Any objections? No, that's sounds fine! Edit -- I'll expand just a bit on that. I agree t . . .
|
Simple Validation
» General Discussion
|
January 29, 2010 09:53
by: hugoheden
|
