When an SF datebox control is dropped on a form, the IgnoreManageReadOnlyState property defaults to True.  All the other SF controls that I have tested default that property to False.

Sam Tenney

I also just noticed a property on the SF datebox control named VerifyDates that refers to MaxFutureDays and MaxPriorDays.  I cannot find any definitions of MaxFutureDays or MaxPriorDays anywhere in the framework.

Sam Tenney

I've sent this to the developers to look at. The comments for the VerifyDates method is wrong and likely indicated an intention to do something more general than was actually coded. The end of the comment is correct. If this is true, acknowledgment is required if the date is in the future or more than 30 days in the past. I'll let you know what I find out.

If MaxFutureDays and MaxPriorDays were public properties on the datebox, they could be very useful in calendaring or scheduling systems.  With any luck maybe these are ideas that will be implemented soon.

Sam Tenney

Sam,



I got the answers related to your questions from the developers.



The IgnoreManageReadOnlyState default is set to true because there is a change overall philosophy on maintenance programs. The original philosphy was to require the user to explicitly indicate they were editing. Over the years we have learned that requiring the end-user to turn on "edit" mode requires additional energy, clicks, and time by the end-user. That is why the maintenance form toolstrip has been modified as well to support this type of logic. It isn't that big of a deal to have to turn this on by the developer, but overall, more developers have gone the way of automatic edit mode. That is why the IsDirtyChanged event was introduced.



The comment was changed (it'll be in the next build) on the DateBox. The min and max won't be used as that is not the intent of the method. The intent of this field is to provide basic low level validation (is the value entered a date). The reason is that instead of trying to program business logic at the control level, it should be controlled through the BO. You would provide business level checks in the CheckRulesOnCurrentRow event handler, that way no matter how the data gets entered, it gets validated appropriately.