You searched for the word(s): userid:638605

More Search Options

RSS Available

• Re: body onload event - timing problem?

  I found my problem. I was overwriting Atlas's Event object with my own. It wasn't an issue until I started using Atlas, of course.

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by Thasmin on 1/1/2006

• Re: body onload event - timing problem?

  My problem might be related to the fact that I have two frames that have the same Atlas web reference. The problem was that in Debug/AtlasRuntime.js on lines 971, 981 and 988, baseName was not defined. It was defined on one frame and not the other. Specifically, I have two columns and it was defined in the first frame but not the second. I looked in AtlasCompat.js and replaced baseName with localName and that made it work fine. Hope this helps for the next CTP.

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by Thasmin on 1/1/2006

• Re: body onload event - timing problem?

  I found out why it wasn't working on IE. It now works and I'm still trying to find out why it's not working in Firefox.

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by Thasmin on 1/1/2006

• Re: body onload event - timing problem?

  I take the last post back. I'm having a lot of trouble getting the web service proxy to work even in IE. My code looks like this: // pageLoad is the Atlas load event function pageLoad() { alert(SimpleWS); }

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by Thasmin on 1/1/2006

• Re: body onload event - timing problem?

  Putting my webservice call in a function called pageLoad instead of one that's called by the body's onLoad event seems to work in IE but not in Firefox 1.07. I just upgraded Firefox to version 1.5 and it still gives the same error.

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by Thasmin on 1/1/2006