On 7/21/06, Thomas Fuchs <[EMAIL PROTECTED]> wrote:
AFAIK the setTimeout makes sure that the eval() is executed in the window-global context, and not the local execution context of the method it happens to be in.
The way Prototype.js uses setTimeout doesn't do this as I noted in another post. There is a way to do what you suggest. I just learned about this approach. http://groups.google.com/group/comp.lang.javascript/tree/browse_frm/thread/f4cb3fae3eb9ea4c/60b52777163fe8ac?rnum=1&hl=en&_done=%2Fgroup%2Fcomp.lang.javascript%2Fbrowse_frm%2Fthread%2Ff4cb3fae3eb9ea4c%3Fhl%3Den%26#doc_89bc83a21339f05a _______________________________________________ Rails-spinoffs mailing list Rails-spinoffs@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
