6 messages in com.perforce.perforce-userYee ha! Was "Re: Can't retrieve by da...
FromSent OnAttachments
Pete...@auspex.com13 Mar 1998 15:00 
WesP...@xmission.com17 Mar 1998 18:57 
Kevi...@Auspex.Com18 Mar 1998 12:11 
WesP...@xmission.com18 Mar 1998 13:45 
Pete...@auspex.com18 Mar 1998 13:55 
Kevi...@Auspex.Com18 Mar 1998 14:03 
Subject:Yee ha! Was "Re: Can't retrieve by date?"
From:WesP...@xmission.com (WesP@xmission.com)
Date:03/18/1998 01:45:17 PM
List:com.perforce.perforce-user

Now you have to decide what 'closest to date xxx' means. What if you have two changes, one exactly twelve seconds before and one exactly twelve seconds after the specified date? Do you stick with closest before, closest after, before if there is one and after if not, or what?

The correct answer is that "closest" always means "closest before". If I want to see the depot as of a certain date that has to mean to show me all of the changes in the depot UP TO AND INCLUDING that date, but certainly not "right after" that date (even if it's only 12 seconds. :) )

Unless there aren't *any* before, in which it's the first one. Right?

I agree with your answer, but features like this have to be carefuly thought out, coded, and then tested in a human factors lab to make sure you're not *surprising* the majority of your customers. ;^)

--- "Where am I, and what am I doing in this handbasket?"

Wes Peters Softweyr LLC http://www.xmission.com/~softweyr softweyr at xmission.com