Comments on: Dealing with asynchronous events, part 3 http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/ music, technology, interfaces, people Mon, 19 Oct 2009 16:37:14 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: AS3 programming 101 for C/C++ coders - Geeky Derek http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/comment-page-1/#comment-283151 AS3 programming 101 for C/C++ coders - Geeky Derek Mon, 25 May 2009 04:19:59 +0000 http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/#comment-283151 [...] the issues of quot;Dealing with asynchronous eventsquot;. So far, he has Part 1, Part 2, and Part 3 available. I strongly recommend reading these articles. They provide a lot of good information for [...] [...] the issues of quot;Dealing with asynchronous eventsquot;. So far, he has Part 1, Part 2, and Part 3 available. I strongly recommend reading these articles. They provide a lot of good information for [...]

]]> By: veeky学习笔记» Blog 存档 » 处理异步事件，第三部分 http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/comment-page-1/#comment-97295 veeky学习笔记» Blog 存档 » 处理异步事件，第三部分 Fri, 23 Nov 2007 14:12:54 +0000 http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/#comment-97295 [...] 原文地址：http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/ [...] [...] 原文地址：http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/ [...]

]]> By: Florecista’s Weblog http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/comment-page-1/#comment-55252 Florecista’s Weblog Mon, 10 Sep 2007 05:41:34 +0000 http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/#comment-55252 [...] Dealing with asynchronous events, part 3 [...] [...] Dealing with asynchronous events, part 3 [...]

]]> By: JCarver http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/comment-page-1/#comment-30675 JCarver Sat, 09 Jun 2007 01:41:55 +0000 http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/#comment-30675 Through blind luck I managed to get it working: call.addResponder(new mx.rpc.Responder(getAlbumInfoResult, null)); Still trying to work out why you have to add a reference to the package. I tried using an "import mx.rpc.Responder;" statement but got a different error which seemed to indicate there was more than one Responder class and that the compiler wasn't sure which one I meant. Thanks again for the great article. Through blind luck I managed to get it working:
call.addResponder(new mx.rpc.Responder(getAlbumInfoResult, null));

Still trying to work out why you have to add a reference to the package. I tried using an “import mx.rpc.Responder;” statement but got a different error which seemed to indicate there was more than one Responder class and that the compiler wasn’t sure which one I meant. Thanks again for the great article.

]]> By: JCarver http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/comment-page-1/#comment-30674 JCarver Sat, 09 Jun 2007 01:26:11 +0000 http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/#comment-30674 OK, call me stupid. Just starting with FLEX... According to the LiveDocs, AsyncToken does NOT have a responder property. It does have a responders property but it is a read-only array. It also has an addResponder() method which SHOULD allow the code in your example to work something like this: call.addResponder(new Responder(getAlbumInfoResult, null)); Unfortunately, this doesn't work either. FlexBuilder complains with "1067: Implicit coercion of a value of type flash.net:Responder to an unrelated type mx.rpc:IResponder.". I don't have enough understanding of the language yet to resolve this issue so will have to try something else. Could you please indicate how this is supposed to work. Thanks. OK, call me stupid. Just starting with FLEX…
According to the LiveDocs, AsyncToken does NOT have a responder property. It does have a responders property but it is a read-only array. It also has an addResponder() method which SHOULD allow the code in your example to work something like this:
call.addResponder(new Responder(getAlbumInfoResult, null));

Unfortunately, this doesn’t work either. FlexBuilder complains with “1067: Implicit coercion of a value of type flash.net:Responder to an unrelated type mx.rpc:IResponder.”. I don’t have enough understanding of the language yet to resolve this issue so will have to try something else.

Could you please indicate how this is supposed to work. Thanks.

]]> By: kuwamoto.org » Blog Archive » Asynchronous calls explained http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/comment-page-1/#comment-21211 kuwamoto.org » Blog Archive » Asynchronous calls explained Wed, 25 Apr 2007 17:24:05 +0000 http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/#comment-21211 [...] Note that this is a more basic (and common?) case than the stuff I was talking about earlier. For more advanced solutions, see here, here and here. From: XXXX@XXXXXXXXX [...] [...] Note that this is a more basic (and common?) case than the stuff I was talking about earlier. For more advanced solutions, see here, here and here. From: XXXX@XXXXXXXXX [...]

]]> By: Dreamer http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/comment-page-1/#comment-2602 Dreamer Thu, 17 Aug 2006 08:27:47 +0000 http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/#comment-2602 Hi Sho, I come back and want to translate this series of posts into Chinese.Your posts are so great. Thanks Hi Sho,

I come back and want to translate this series of posts into Chinese.Your posts are so great.

Thanks

]]> By: Ele http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/comment-page-1/#comment-2422 Ele Sun, 30 Jul 2006 09:26:41 +0000 http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/#comment-2422 Anyway, that’s just my 2 cents: I think ECMA compliance is a bullet-point feature that could easily be binned. People aren’t choosing to develop in flash because the language is standards compliant, they’re choosing to develop in flash because of what it allows them to do on the web. I’d personally rather have a language that helped me find bugs before runtime than to have one that happens to be somewhat similar to javascript. Anyway, that’s just my 2 cents: I think ECMA compliance is a bullet-point feature that could easily be binned. People aren’t choosing to develop in flash because the language is standards compliant, they’re choosing to develop in flash because of what it allows them to do on the web. I’d personally rather have a language that helped me find bugs before runtime than to have one that happens to be somewhat similar to javascript.

]]> By: mike ross http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/comment-page-1/#comment-783 mike ross Wed, 31 May 2006 01:18:20 +0000 http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/#comment-783 thanks sho, for taking the time to explain that to me. I understand it better now. -mike. thanks sho, for taking the time to explain that to me. I understand it better now. -mike.

]]> By: Ray Greenwell http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/comment-page-1/#comment-777 Ray Greenwell Tue, 30 May 2006 20:52:44 +0000 http://kuwamoto.org/2006/05/19/dealing-with-asynchronous-events-part-3/#comment-777 Sho, Thanks for taking the time to respond to me. I can respect the desire to keep the language a dynamic language at its core. I wonder if it would be possible to add a new compiler directive called -warndynamic, or -superstrict or something, that warned of any accesses to properties that are not defined at compile time. Just a thought. Sho,

Thanks for taking the time to respond to me. I can respect the desire to keep the language a dynamic language at its core.

I wonder if it would be possible to add a new compiler directive called -warndynamic, or -superstrict or something, that warned of any accesses to properties that are not defined at compile time. Just a thought.

]]>