Comments on: Sneaky Flex trick to get the name of any calling functions http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/ A blog about Adobe Flex Tue, 16 Mar 2010 15:47:29 +0000 http://wordpress.org/?v=abc hourly 1 By: The getStackTrace Super Bug @ Bill White’s Blog http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/comment-page-1/#comment-208246 The getStackTrace Super Bug @ Bill White’s Blog Mon, 03 Aug 2009 23:44:40 +0000 http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/#comment-208246 [...] made good use of a tip I picked up from McCune on generating a stacktrace in my logging statements so that I can not only see the method that was [...] [...] made good use of a tip I picked up from McCune on generating a stacktrace in my logging statements so that I can not only see the method that was [...]

]]> By: The Error.getStackTrace() Smart Bug @ Bill White’s Blog http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/comment-page-1/#comment-208232 The Error.getStackTrace() Smart Bug @ Bill White’s Blog Thu, 30 Jul 2009 21:07:30 +0000 http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/#comment-208232 [...] made good use of a tip I picked up from McCune on generating a stacktrace in my logging statements so that I can not only see the method that was [...] [...] made good use of a tip I picked up from McCune on generating a stacktrace in my logging statements so that I can not only see the method that was [...]

]]> By: JC http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/comment-page-1/#comment-61911 JC Mon, 03 Mar 2008 20:10:47 +0000 http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/#comment-61911 Keep in mind that if you're running the debugger, you can see the stack trace at any time within the Debug panel. What's also nice is that if you're on a breakpoint, you can click on any of the items in the stack in that panel to switch to that object's context, ie: be able to see its variables and such. Very handy stuff. Keep in mind that if you’re running the debugger, you can see the stack trace at any time within the Debug panel. What’s also nice is that if you’re on a breakpoint, you can click on any of the items in the stack in that panel to switch to that object’s context, ie: be able to see its variables and such. Very handy stuff.

]]> By: George Cook http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/comment-page-1/#comment-59677 George Cook Wed, 27 Feb 2008 09:43:20 +0000 http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/#comment-59677 I was sent here by a colleague who reckoned I'd love this hacky solution. He was damn right! Lovely ! Thanks :) I was sent here by a colleague who reckoned I’d love this hacky solution. He was damn right!

Lovely !

Thanks :)

]]> By: Almog Kurtser http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/comment-page-1/#comment-58373 Almog Kurtser Fri, 22 Feb 2008 18:15:25 +0000 http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/#comment-58373 Hi, that's really nice monkey you've got :) I think Theo and Johannes are right, mxmlc keeps the stack trace in both debug and release, it's a matter of flash player version. I wasn't aware of the verbose-stacktraces Theo blogged about. I guess maybe the reason they left that information in the release swf by default is to enable developers logging their apps. Hmm..and maybe not. Cheers, Almog Kurtser. Hi,

that’s really nice monkey you’ve got :)

I think Theo and Johannes are right, mxmlc keeps the stack trace in both debug and release, it’s a matter of flash player version.
I wasn’t aware of the verbose-stacktraces Theo blogged about.
I guess maybe the reason they left that information in the release swf by default is to enable developers logging their apps.
Hmm..and maybe not.

Cheers,
Almog Kurtser.

]]> By: Glenn Williams http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/comment-page-1/#comment-58356 Glenn Williams Fri, 22 Feb 2008 15:23:17 +0000 http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/#comment-58356 Hi, nice little trick. Is that a new version of flexSpy, or just one you've hacked together. I'll like the source if you're making it available. cheers glenn Hi,

nice little trick.

Is that a new version of flexSpy, or just one you’ve hacked together. I’ll like the source if you’re making it available.

cheers
glenn

]]> By: johannes http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/comment-page-1/#comment-58340 johannes Fri, 22 Feb 2008 12:36:49 +0000 http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/#comment-58340 as you have the debug player it should work. try on a virgin machine with the normal runtime. arguments.caller was very handy for event listener clean up in the past, pity tis gone when using anon functions with event listeners. as you have the debug player it should work. try on a virgin machine with the normal runtime.

arguments.caller was very handy for event listener clean up in the past, pity tis gone when using anon functions with event listeners.

]]> By: Theo http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/comment-page-1/#comment-58338 Theo Fri, 22 Feb 2008 12:21:11 +0000 http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/#comment-58338 The source paths in square brackets comes from the verbose-stacktraces compiler flag. See my post on the subject: http://blog.iconara.net/2007/11/22/mxmlc-wtf-7-snooping-with-verbose-stacktraces/ The source paths in square brackets comes from the verbose-stacktraces compiler flag. See my post on the subject: http://blog.iconara.net/2007/11/22/mxmlc-wtf-7-snooping-with-verbose-stacktraces/

]]> By: Doug http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/comment-page-1/#comment-58247 Doug Fri, 22 Feb 2008 03:13:14 +0000 http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/#comment-58247 @Alan, hmm, interesting. All I know is that in my blog post I tried embedding a version of the app that I exported as a release build with FB 3 B3 and the getStackTrace() stuff didn't work when I viewed it on the web page (maybe my player didn't know it was supposd to be in debug mode?). So then I just re-uploaded the version that was the normal debug swf and it all worked fine for me. @Alan, hmm, interesting. All I know is that in my blog post I tried embedding a version of the app that I exported as a release build with FB 3 B3 and the getStackTrace() stuff didn’t work when I viewed it on the web page (maybe my player didn’t know it was supposd to be in debug mode?). So then I just re-uploaded the version that was the normal debug swf and it all worked fine for me.

]]> By: Alan Shaw http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/comment-page-1/#comment-58241 Alan Shaw Fri, 22 Feb 2008 02:46:26 +0000 http://dougmccune.com/blog/2008/02/21/sneaky-flex-trick-to-get-the-name-of-any-calling-functions/#comment-58241 Although the documentation says getStackTrace() will return null if not using the debugger version of the player, that doesn't mean that it will return null in a release build played in the debugger version of the player. The source information in the square brackets is missing, but the function names are still there. This version of functionName() works for me in either a debug or release build (current FB 3 beta): package { public function functionName():String { var s:String = new Error().getStackTrace(); s = s.substring(s.indexOf("at") + 2); var i:int = s.indexOf("at") + 3; var j:int = s.indexOf("()", i); return s.substring(i, j); } } Although the documentation says getStackTrace() will return null if not using the debugger version of the player, that doesn’t mean that it will return null in a release build played in the debugger version of the player. The source information in the square brackets is missing, but the function names are still there. This version of functionName() works for me in either a debug or release build (current FB 3 beta):

package
{
public function functionName():String
{
var s:String = new Error().getStackTrace();
s = s.substring(s.indexOf(“at”) + 2);
var i:int = s.indexOf(“at”) + 3;
var j:int = s.indexOf(“()”, i);
return s.substring(i, j);
}
}

]]>