Here's what I would do. Hope this makes sense:
[0] On key down, set some global state variable to true.
[1] On key up, set the state variable to false.
[1a] Then use setTimeout() to have it call a new function in 1 second
(adjust for usability).
[2] Your new function will look to to see if
The two versions have a number of subtle but remarkable differences
that makes it difficult to do a side-by-side comparison. One's
faster, one rotates the photographs, one bounces them around a bit
upon reaching their destination. For what it's worth, running XP Pro
SP 3 / FF 3, I prefer the impl
This will also likely create a ton of 404s for the bogus image
requests that are made prior to your JS fixing the image URLs. If
your client likes to look at web logs to identify broken links, this
will become a headache.
I'm going to echo everyone else's sentiments that this is a bad idea.
This
mojoeJohn,
You have an extra trailing comma in "speed: 4000,", which is
definitely going to give you trouble in IE. IE is less forgiving of
JS syntax errors than, for example, FF.
You might find this useful: http://www.jslint.com/
Hope that helps.
Mark
IE is (rightfully) less forgiving of
4 matches
Mail list logo