f
All the best.
Clouds.
--
From: "Karina Steffens" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: lingo-l check my simple code.
Date: Mon, Sep 25, 2000, 9:25 PM
I've had to deal with international time issues myslef, so here's a code I
developed that should parse the time corre
Hi,
Don't know if it's a localization problem (I'm running a french Win2k), but
the long time returns me format like :
put the long time
-- "13:38:14 "
Withouy any AM or PM considerations... this might make your test failed.
Such minor modifs I've made and try successfully : (but Iv've not set
Hi, could anyone please take some time to check my simple code? I can't get
the correct output. I think there must be something wrong with my logic.
Sorry to waste you gays time. Thanks.
As SP has shown, there are international issues. You can get around
that by using the systemdate().seconds
Hi, Colin Holgate, I got an error message when I use the
systemdate().seconds function. What's wrong is it? (I'm using D7) Please
help. Thanks.
--
From: Colin Holgate [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: lingo-l check my simple code.
Date: Sun, Sep 24, 2000, 10:24 PM
Hi, Colin Holgate, I got an error message when I use the
systemdate().seconds function. What's wrong is it? (I'm using D7) Please
help. Thanks.
Sorry about that, it looks like the seconds part came in with
Director 8. You may have to do some work to figure out the time
format for the country
Hi, could anyone please take some time to check my simple code? I can't get
the correct output. I think there must be something wrong with my logic.
Sorry to waste you gays time. Thanks.
global gName
on getTimer me
CurrentTime = the long time
if currentTime = "12:00:00 AM" and currentTime
