|
Timer
Feb 5, 2007 23:15:13 GMT
|
Greg says: Coding music... Greg says: Hmm... Greg says: I wouldn't rule it out. Chris 3.0 [New features? Yes.] says:
Greg says: If you think about machine code it's a bunch of 1s and 0s Chris 3.0 [New features? Yes.] says: Anything is possible. Greg says: Yeah try to code Metallica Chris 3.0 [New features? Yes.] says: Yeah, I'll get right on that... right after I learn to fly.
|
|
|
|
|
Timer
Feb 6, 2007 2:40:07 GMT
That's actually very weird. Up until I uploaded it was working fine in FF. In IE it works perfect. I am rather confused by it right now. I guess I will play around more. Edit: I noticed webpost is using a setTimeout function do you think this could be causing a problem in FF?
Last Edit: Feb 6, 2007 2:43:16 GMT by Moose
|
Greg says: Coding music... Greg says: Hmm... Greg says: I wouldn't rule it out. Chris 3.0 [New features? Yes.] says:
Greg says: If you think about machine code it's a bunch of 1s and 0s Chris 3.0 [New features? Yes.] says: Anything is possible. Greg says: Yeah try to code Metallica Chris 3.0 [New features? Yes.] says: Yeah, I'll get right on that... right after I learn to fly.
|
|
|
|
Timer
Feb 7, 2007 0:40:14 GMT
That's actually very weird. Up until I uploaded it was working fine in FF. In IE it works perfect. I am rather confused by it right now. I guess I will play around more. Edit: I noticed webpost is using a setTimeout function do you think this could be causing a problem in FF? 'All depends on how it's written, what it does, and how slow a connection the user has.
|
|
|
|
Timer
Feb 10, 2007 0:40:02 GMT
Personally, I'd drop the setTimeout to 1 and then use the date.getTime to update the clock's accuracy. That way you can do milliseconds too if needed.
|
|
|
|