Thank you Peter.
On 1/3/07, Peter Farland <[EMAIL PROTECTED]> wrote:
Sorry, that is, a public wrapper function:
package
{
public function global_trace(...rest:Array):void
{
trace(rest);
}
}
--
Derek Vadneau
Sorry, that is, a public wrapper function:
package
{
public function global_trace(...rest:Array):void
{
trace(rest);
}
}
> When I type "flash.utils.t", trace(rest:Array):void
> is displayed. So, I assumed it was still defined there
> but just included/imported by default.
This is a mistake, sorry about that.
> So, is there a way to specify that I want the
> "global" trace function rather than my class-defined
> tr
---
*From:* flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] *On
Behalf Of *Sascha
*Sent:* Tuesday, January 02, 2007 11:28 AM
*To:* flexcoders@yahoogroups.com
*Subject:* RE: [flexcoders] Call to a possibly undefined method trace
Why would it be dumb to use trace? I
com
Subject: RE: [flexcoders] Call to a possibly undefined method trace
Why would it be dumb to use trace? It's a neat way of doing a quick
debug. The debugger is not always the best choice.
Not sure why the trace will not work when called with the whole package
name, probably because it's build i
Sascha
_
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Derek Vadneau
Sent: Wednesday, 03 January, 2007 01:07
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Call to a possibly undefined method trace
I have a class that has a method called trace. I wanted to
I have a class that has a method called trace. I wanted to test that
method so I used trace ... I know, dumb. Anyhow, I tried using
flash.utils.trace(message) to specify the trace I wanted to execute.
That gives me a compile error: Call to a possibly undefined method
trace.
Perhaps this is academi
7 matches
Mail list logo
