Understanding the Convert Command

[Gregory Lypny]

Thanks for clearing that up Sarah!  I'm bewildered why a bug such as 
this would be left unfixed for so long given the importance of date 
comparisons and calculations in many applications.

	Gregory Lypny
	__________________________
	Associate Professor of Finance
	John Molson School of Business
	Concordia University
	Montreal, Canada


On Nov 22, 2004, at 12:59 AM, use-revolution-request at lists.runrev.com 
wrote:

> Hi Greg,
>
> No need for confusion or embarrassment :-)
> This is a known bug that I was ranting about for months but I thought
> it had been fixed in Rev 2.5 - what version are you using?
>
> Here is a link to the bug which will give you all the info.
> <http://support.runrev.com/bugdatabase/show_bug.cgi?id=1162>
>
> I wrote a bugFixConvert routine to do conversions without adding the
> hour and I have also written a routine that uses AppleScript to find
> the number of minutes or seconds of daylight saving currently in use.
> If you would like either of these, email me off-list.
>
> Cheers,
> Sarah
> sarahr at genesearch.com.au
> http://www.troz.net/Rev/
>
> On 20 Nov 2004, at 4:23 pm, Gregory Lypny wrote:
>
>> Having trouble understanding the Convert command.  I'm playing with
>> the following handler and using day/month/year format.
>>
>> on mouseUp
>>   set useSystemDate to true
>>   get fld "date"
>>   convert it to long date and long time
>>   put it into fld "converted date"
>> end mouseUp
>>
>> The online documentation for the Convert command notes:
>>
>> "If you convert a date without a time to a form that includes the
>> time, the time will be given as 2 AM. (This is the default time
>> because it is the time of day when Daylight Savings Time begins and
>> ends.)"
>>
>> If I enter 1/10/2004 in the date field, I get Friday, October 01, 2004
>> 3:00:00 AM, which is not 2 AM.  And if I enter 1/10/2004 0:00:00, I
>> get Friday, October 01, 2004 1:00:00 AM.