Oh, one other idea... Set *both* properties in each set, that way you
can make sure they're a valid pair.
E.g.
Public property Minimum
{
get{...}
set
{
min = value;
if( max < min )
max = min;
}
}
...and vice-versa. I think that would work OK in the designer.
G.
-----Original Message-----
From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf Of
Chris Sells
Sent: 17 May 2002 19:35
To: [EMAIL PROTECTED]
Subject: Re: Setting properties
That doesn't work with components in the designer.
Chris Sells
http://www.sellsbrothers.com/
> -----Original Message-----
> From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf
Of
> Sills, Adam
> Sent: Friday, May 17, 2002 11:41 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [DOTNET] Setting properties
>
> Why not just make a setter method and leave your properties readonly.
>
> -----Original Message-----
> From: Chris Sells [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 17, 2002 2:27 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [DOTNET] Setting properties
>
>
> I ran into this issue just the end day with a start date and an end
date. I
> couldn't figure out how to check that the start was always before the
end
> without requiring them to set the properties in a certain order.
You can read messages from the DOTNET archive, unsubscribe from DOTNET,
or subscribe to other DevelopMentor lists at http://discuss.develop.com.
You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
