Yes, abstract validation package (not tied to GUI) is project.validator. You
should add class name checking code to:
...project.validator.ObjEntityValidator.validateObject();
Modeler will pick it up automatically.
Andrus
Craig Miskell writes:
> Ahhh, I see where you're going. Yes, that is much "saner". Some help
> would be good, mainly to point me to the relevant classes. I'm guessing
> maybe project.validator package, but I'm not 100% certain.
>
> Craig
> On Wed, 2002-11-20 at 09:03, Andrus Adamchik wrote:
>> Craig,
>>
>> since "addObjEntity" is mainly used by the modeler, shouldn't we remove all
>> the checks at all, and rather move them to the validation package?
>>
>> I think we should allow saving multiple entities with the same class name
>> (even if it is not null), just give a validation warning. When working on
>> the Modeler I discovered that any tight data structures make the tool very
>> unfriendly, since they don't allow saving partial work.
>>
>> Let me know if you need help on doing validation.
>>
>> Andrus
>>
>>
This archive was generated by hypermail 2.0.0 : Tue Nov 19 2002 - 15:21:52 EST