Atlas 6: When 'this' is not really 'this'

re: Atlas 6: When 'this' is not really 'this'

Tim Scarfe — Sun, 26 Nov 2006 02:37:02 GMT

Shame I missed this one at the time.. :)

This problem always was a classic in javascript i.e. closures get executed in global scope - but the workaround is this:

function SampleClass()

{

this.id = 1;

this.call = function()

{

var obj = this;

PageMethods.DoSomething( "Hi", function(result)

{

debug.dump( obj.id );

} );

}

I feel like it's 1999 again ;)

re: Atlas 6: When 'this' is not really 'this'

Murali — Fri, 03 Nov 2006 06:42:52 GMT

Hi I have a weird problem with Pagemethods as well: 1. I use "PageMethods" to call the function on the ASPX Page. This method is a static method and it is **NOT IN** my code behind file. It is decorated by "webmethod" and "scriptmethod" attributes as required by Ajax Extensions Beta 1. I use javascript to invoke the "PageMethods." on click of a button. 2. The called method returns a message from resource file at the folder App_GlobalResources. I have 2 variations of the resource file (ta-IN and the base en-US) 3. The page culture is set to "auto" and uiculture also "auto" 4. In my internet explorer , languages section I have kept "ta-IN" as first preference and "en-US" as second. 5. When the page is loaded all the controls are localized correctly to "ta-IN". But atlas callbacks using "PageMethods." do not recognize the culture and always return the string from "en-US" files. 6. I debugged a call back to find System.Threading.Thread.CurrentCulture and System.Threading.Thread.CurrentUICulture as "en-US" during callbacks whereas other page processing events such as PageLoad , prerender it is correctly set to "ta-IN". So the question is how do I get my callbacks to return correct strings in sync with the page localization. Thanks for your time and effort.

re: Atlas 6: When 'this' is not really 'this'

Dav Evans — Wed, 18 Oct 2006 06:07:04 GMT

Hi Omar. I am having the problem you described above where Atlas is returning after a webservice call into a different context, and so "this" no longer refers to the javascript class that made the original call. Unfortunately your solution of using the following client-side code: function SampleClass() { this.id = 1; this.call = function() { PageMethods.DoSomething( "Hi", Function.createDelegate( this, function(result) { debug.dump( this.id ); } ) ); } } isnt working for me. when I execute the call method, I get back null rather than "1" (the id specified in the class). Any ideas how I might get the callback to be in the context of my class so that I can refer to other members of the class? Thanks