> > procedure MyComponent.SetEnableSecurity (Value: Boolean);
> > begin
> > FEnableSecurity := Value;
> > if not FEnableSecurity then
> > ShowMessage ('Warning: MySecurityComponent1.EnableSecurity is off.');
> > end;
>
> Yeh well, if you have that in about 5-6 places, different components with
> different warnings/messages, it would soon get irratating. And be more in
> that way than anything else. I would see this ability much like a
> property editor, but we could call it a property constrainer, or
> something. Or it could even be an extension of the property editor itself
> (which I actually think would be a good place for it).
I'd assumed Mark meant something like
procedure MyComponent.SetEnableSecurity (Value: Boolean);
begin
FEnableSecurity := Value;
{$WARN MyComponent.SetEnableSecurity does not trigger an OnChange event}
end;
Allowing a compile to give feedback through the compiler for unfinished or untested
code.
It's possible the To-Do lists in D5 might fill enough of this wishes shoes.
--
Aaron Scott-Boddendijk
Jump Productions
(07) 838-3371 Voice
(07) 838-3372 Fax
---------------------------------------------------------------------------
New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
