That's weird. I still get the 16th. Can anyone else confirm the 15th? (not
doubting you Dar)
I might have to change this then…
Tom
-- Tom McGrath III
http://lazyriver.on-rev.com
mcgra...@mac.com
On Jul 18, 2013, at 12:39 AM, Dar Scott d...@swcp.com wrote:
On Jul 17, 2013, at 7:03 PM,
Hi Tom,
Am 18.07.2013 um 17:56 schrieb Thomas McGrath III mcgra...@mac.com:
That's weird. I still get the 16th. Can anyone else confirm the 15th? (not
doubting you Dar)
I might have to change this then…
I think you can simply add two hours (2*600) to the resulting seconds and are
safe :-)
I think it is the UTC seconds thing. I think that changing a date to seconds
will get midnight of the day for the current time zone. Somebody in an more
westerly timezone might see those seconds and the date will be earlier.
If it is on only one computer and the timezone will not change,
it gets midnight UTC, livecode changing the date FROM the time zone
independent seconds gives you time zone differences.
On Thu, Jul 18, 2013 at 12:48 PM, Dar Scott d...@swcp.com wrote:
I think it is the UTC seconds thing. I think that changing a date to
seconds will get midnight of the day
disregard, after looking more closely at his email dar is correct
completely.
On Thu, Jul 18, 2013 at 1:01 PM, Andrew Kluthe and...@ctech.me wrote:
it gets midnight UTC, livecode changing the date FROM the time zone
independent seconds gives you time zone differences.
On Thu, Jul 18, 2013
We might be saying the same thing, but I'm not sure.
on mouseUp
get the short date
convert it to seconds
put it tab it/3600 mod 24
end mouseUp
gives me this:
1374127200 6
I'm in MDT (Rocky Mountains), somebody in California might take those same
seconds and convert to a short
I am converting the short date (08/16/13) to seconds and I get 1376625600
My question is Is the converted seconds always that many digits when converted
from that type of date?
The reason I ask is I am making filenames by merging a name like Thomas or
Tom with the date converted to seconds as
Since its the number of seconds since.. I think 1970, there will always be
that many digits at least until the odometer rolls up to 99 + 1.
Plenty of breathing space there.
On Wed, Jul 17, 2013 at 7:03 PM, Thomas McGrath III mcgra...@mac.comwrote:
I am converting the short date
Will the create of file names be in the same time zone as the reader of file
names?
On Jul 17, 2013, at 7:03 PM, Thomas McGrath III wrote:
I am converting the short date (08/16/13) to seconds and I get 1376625600
My question is Is the converted seconds always that many digits when
LiveCode use-livecode@lists.runrev.com
Sent: Wed, Jul 17, 2013 9:21 pm
Subject: Re: Convert date to seconds
Will the create of file names be in the same time zone as the reader of file
names?
On Jul 17, 2013, at 7:03 PM, Thomas McGrath III wrote:
I am converting the short date (08/16/13
of the seconds, and if it is eleven then modify your chunk stuff.
Craig Newman
-Original Message-
From: Dar Scott d...@swcp.com
To: How to use LiveCode use-livecode@lists.runrev.com
Sent: Wed, Jul 17, 2013 9:21 pm
Subject: Re: Convert date to seconds
Will the create of file names
Tom-
Wednesday, July 17, 2013, 6:03:26 PM, you wrote:
The reason I ask is I am making filenames by merging a name like
Thomas or Tom with the date converted to seconds as in
Thomas1376625600.txt or Tom1376625600.txt
Regex to the rescue:
get matchtext(tFileName, ([A-Za-z]+)([0-9]+), tName,
Mike-
Wednesday, July 17, 2013, 6:53:41 PM, you wrote:
Could work up a simple regex and use matchtext instead to remove the issue
entirely also.
Ha! GMTA
--
-Mark Wieder
mwie...@ahsoftware.net
___
use-livecode mailing list
GMTA? Did that mean I won?!?!?! *cough*
On Wed, Jul 17, 2013 at 8:25 PM, Mark Wieder mwie...@ahsoftware.net wrote:
Mike-
Wednesday, July 17, 2013, 6:53:41 PM, you wrote:
Could work up a simple regex and use matchtext instead to remove the
issue
entirely also.
Ha! GMTA
--
-Mark
14 matches
Mail list logo
