Re: [WebDNA] seconds_to_time
This WebDNA talk-list message is from 2017
It keeps the original formatting.
numero = 113472
interpreted = N
texte = 1067 --Apple-Mail=_E1D8BF0A-3DA9-494D-A8B1-0F42802C6DC3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 G=E2=80=99day Grant !! OK, I understand now, the first second of the day is actually 0 so then = the last will be 86399. So then [MATH]{24:00:00}[/MATH] resolves to 86400 & 00:00:00 resolves to = 0, but in fact they are both the same time. The problem is that if you save 24:00:00 as 86400 and then try to write = it back to 24:00:00 you get 00:00:00. I need to rethink this - maybe = restrict the =E2=80=98clock=E2=80=99 to 23:59:59. Kind regards Stuart Tremain Pharoah Lane Software AUSTRALIA webdna@idfk.com.au > On 20 Mar 2017, at 15:43, Grant Hulbert
= wrote: >=20 > 23:59:59 is the last second of a day; 24:00:00 doesn't exist. 00:00:00 = is the beginning of the next day. >=20 > Remember that numbers are zero-based, so 86,400 seconds in a day = really means the range of seconds 0 through 86399. 86,400 would be the = first second of the *next* day. >=20 > On Sun, Mar 19, 2017 at 8:32 PM, Stuart Tremain > wrote: > Why does this=20 >=20 > [FORMAT seconds_to_time]86400[/FORMAT] >=20 > convert to 00:00:00, I would have thought that it should be 24:00:00 >=20 >=20 >=20 > Kind regards >=20 > Stuart Tremain > Pharoah Lane Software > AUSTRALIA > webdna@idfk.com.au >=20 >=20 >=20 >=20 >=20 >=20 > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us = Bug Reporting: = support@webdna.us > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us --Apple-Mail=_E1D8BF0A-3DA9-494D-A8B1-0F42802C6DC3 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 G=E2=80=99day Grant !!
OK, I understand now, the first second of the day is = actually 0 so then the last will be 86399.
So then [MATH]{24:00:00}[/MATH] = resolves to 86400 & 00:00:00 resolves to 0, but in fact they are = both the same time.
The problem is that if you save 24:00:00 as 86400 and then = try to write it back to 24:00:00 you get 00:00:00. I need to rethink = this - maybe restrict the =E2=80=98clock=E2=80=99 to 23:59:59.
Kind regards
Stuart Tremain
Pharoah Lane Software
AUSTRALIA
23:59:59 is the last second of a day; 24:00:00 doesn't exist. = 00:00:00 is the beginning of the next day.
Remember that numbers are zero-based, = so 86,400 seconds in a day really means the range of seconds 0 through = 86399. 86,400 would be the first second of the *next* = day.
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us
= --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us --Apple-Mail=_E1D8BF0A-3DA9-494D-A8B1-0F42802C6DC3-- .
Associated Messages, from the most recent to the oldest:
1067 --Apple-Mail=_E1D8BF0A-3DA9-494D-A8B1-0F42802C6DC3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 G=E2=80=99day Grant !! OK, I understand now, the first second of the day is actually 0 so then = the last will be 86399. So then [math]{24:00:00}[/MATH] resolves to 86400 & 00:00:00 resolves to = 0, but in fact they are both the same time. The problem is that if you save 24:00:00 as 86400 and then try to write = it back to 24:00:00 you get 00:00:00. I need to rethink this - maybe = restrict the =E2=80=98clock=E2=80=99 to 23:59:59. Kind regards Stuart Tremain Pharoah Lane Software AUSTRALIA webdna@idfk.com.au > On 20 Mar 2017, at 15:43, Grant Hulbert = wrote: >=20 > 23:59:59 is the last second of a day; 24:00:00 doesn't exist. 00:00:00 = is the beginning of the next day. >=20 > Remember that numbers are zero-based, so 86,400 seconds in a day = really means the range of seconds 0 through 86399. 86,400 would be the = first second of the *next* day. >=20 > On Sun, Mar 19, 2017 at 8:32 PM, Stuart Tremain > wrote: > Why does this=20 >=20 > [FORMAT seconds_to_time]86400[/FORMAT] >=20 > convert to 00:00:00, I would have thought that it should be 24:00:00 >=20 >=20 >=20 > Kind regards >=20 > Stuart Tremain > Pharoah Lane Software > AUSTRALIA > webdna@idfk.com.au >=20 >=20 >=20 >=20 >=20 >=20 > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us = Bug Reporting: = support@webdna.us > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us --Apple-Mail=_E1D8BF0A-3DA9-494D-A8B1-0F42802C6DC3 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 G=E2=80=99day Grant !!
OK, I understand now, the first second of the day is = actually 0 so then the last will be 86399.
So then
[math]{24:00:00}[/MATH] = resolves to 86400 & 00:00:00 resolves to 0, but in fact they are = both the same time.
The problem is that if you save 24:00:00 as 86400 and then = try to write it back to 24:00:00 you get 00:00:00. I need to rethink = this - maybe restrict the =E2=80=98clock=E2=80=99 to 23:59:59.