Has anyone had any problems with IE being too slow? I am having a problem with running functions right after it was created. dojo.addOnLoad seems to help but I don't want to use that every time.
Has anyone had any problems with IE being too slow? I am having a problem with running functions right after it was created. dojo.addOnLoad seems to help but I don't want to use that every time.
Not really. /* GeSHi (C)
Not really.
What is "it"?
Any javascript creating widgets or addressing them or other dojo actions should be run after dojo has fully loaded. If you have such functions that will be called during the page load, then you should put them in dojo.addOnLoad(...).
Sorry for not explaining
Sorry for not explaining better. The problem I am having is that I am creating multiple dynamic functions and in each function I am creating a dijit Tree. Some of these functions get called right after the function is created.
Example:
This loop could possibly loop up too 40 times.
for loop
{
include a jsp file that contains the function
dynamic function()
{
create dijit tree
}
if( supposed to run function is true )
{
call of function just created.
}
}
This works fine in Firefox but gives me a problem in IE. Of course debugging is horrible in IE but the only thing I could figure out is that if when that function is to be called if I used dojo.addOnLoad it worked. So I was assuming that it was a timing issue. The only thing is that I do this multiple times in different places in the software. If I do this too many times I am afraid that the onload will have to much to do and slow things down. Also I don't believe this is good programming on my part to use the dojo.addOnLoad that many times. This is why I wrote a post because I think I might be doing something wrong.
Thanks in advance!!
John
Well, I don't know. You may
Well, I don't know. You may want to install Nikhil's Web Development Helper from:
http://www.nikhilk.net/WebDevHelperHTTPTracingUpdates.aspx
It is sometimes a bit awkward, but once the console displays in the lower part of the IE browser window, turn on Script Console and Enable Script Debugging. Then run your web app and see if it detects any otherwise silent errors/exceptions.
Otherwise, no ideas...