Re: time anomaly
You should test this first. My test have a slightly different 'result' > So I could say "that appointment is at 2PM", convert it to a date and > time, and have it come up with "today at 2PM". Or 54 would be "the > time right now with the seconds equal to 54". 54 is the seconds, but not (time right now), just the (right HOUR now). Not sure how useful that is. put 54 into tTime convert tTime to long time put tTime --> 16:00:54 until the next hour starts Jim Ault Las Vegas On 8/20/05 9:34 AM, "Mark Wieder" <[EMAIL PROTECTED]> wrote: > Jeanne- > > Friday, August 19, 2005, 7:28:40 PM, you wrote: > >> Actually, it's not indeterminate. When you provide a number or other >> partial date or time, convert guesses what part you mean and fills in >> the rest with the current time. (For example, if you convert a time >> to long data and long time, you get today's date along with the time >> you specified.) This probably should be in the convert docs as a note. > > Cool. > I think. > So I could say "that appointment is at 2PM", convert it to a date and > time, and have it come up with "today at 2PM". Or 54 would be "the > time right now with the seconds equal to 54". ___ use-revolution mailing list [EMAIL PROTECTED] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: time anomaly
Jeanne- Friday, August 19, 2005, 7:28:40 PM, you wrote: > Actually, it's not indeterminate. When you provide a number or other > partial date or time, convert guesses what part you mean and fills in > the rest with the current time. (For example, if you convert a time > to long data and long time, you get today's date along with the time > you specified.) This probably should be in the convert docs as a note. Cool. I think. So I could say "that appointment is at 2PM", convert it to a date and time, and have it come up with "today at 2PM". Or 54 would be "the time right now with the seconds equal to 54". -- -Mark Wieder [EMAIL PROTECTED] ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: time anomaly
At 2:14 PM -0700 8/19/2005, Mark Wieder wrote: > Any idea why this code produces "19:00:54" instead of "54"? I do have > twelveHourTime set to false, but... What you have given it as an argument is not a date, time, nor a date and time, but just a number. I would expect that you would get back an indeterminate answer. I get "4:00:54 PM". At least today. GIGO. Actually, it's not indeterminate. When you provide a number or other partial date or time, convert guesses what part you mean and fills in the rest with the current time. (For example, if you convert a time to long data and long time, you get today's date along with the time you specified.) This probably should be in the convert docs as a note. -- jeanne a. e. devoto ~ [EMAIL PROTECTED] http://www.jaedworks.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: time anomaly
I get the current hour on my computer, "00" minutes, and 54 seconds. with twelvehourtime true => 4:00:54, and false => 16:00:54 using 4 => 16:00:04 using 124 => 16:02:04 (124 seconds past the current hour) using 3600 => 17:00:00 (3600 seconds, or 60 min past the current hour) thus if using only seconds, the function returns the time x seconds after the top of the current hour. Wonder how you could used this? Perhaps in programming a clock. Jim Ault Las Vegas On 8/19/05 12:41 PM, "Brian Yennie" <[EMAIL PROTECTED]> wrote: > This is a guess, but I believe it would be because: > > "The seconds function returns the total number of seconds since > midnight, January 1, 1970 GMT" > > Assuming your timezone is at GMT-5 hours, you are seeing 54 seconds > past January 1, 1970 GMT, otherwise known as December 31, 1969 @ > 19:00:54 > > HTH, > Brian > >> Any idea why this code produces "19:00:54" instead of "54"? I do have >> twelveHourTime set to false, but... >> >> on mouseUp >> local t >> put 54 into t >> convert t to long time >> answer t >> end mouseUp > > ___ > use-revolution mailing list > use-revolution@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: time anomaly
Jon- Friday, August 19, 2005, 12:21:16 PM, you wrote: > Any idea why this code produces "19:00:54" instead of "54"? I do have > twelveHourTime set to false, but... > on mouseUp > local t > put 54 into t > convert t to long time > answer t > end mouseUp Well, I can see why you might think that would work, but... the docs (remember the docs? they come with the package...) say that convert "Changes a date, a time, or a date and time to a specified format" What you have given it as an argument is not a date, time, nor a date and time, but just a number. I would expect that you would get back an indeterminate answer. I get "4:00:54 PM". At least today. GIGO. -- -Mark Wieder [EMAIL PROTECTED] ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: time anomaly
This is a guess, but I believe it would be because: "The seconds function returns the total number of seconds since midnight, January 1, 1970 GMT" Assuming your timezone is at GMT-5 hours, you are seeing 54 seconds past January 1, 1970 GMT, otherwise known as December 31, 1969 @ 19:00:54 HTH, Brian Any idea why this code produces "19:00:54" instead of "54"? I do have twelveHourTime set to false, but... on mouseUp local t put 54 into t convert t to long time answer t end mouseUp ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
time anomaly
Any idea why this code produces "19:00:54" instead of "54"? I do have twelveHourTime set to false, but... on mouseUp local t put 54 into t convert t to long time answer t end mouseUp ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
