I'm new to FAMES so undoubtedly I'm this is something obvious but I've
stepped thru a number of 'Getting Started' tutes without seeing this issue
addressed...
I'm having problems correctly referencing external classes. For example,
attempting to use xRay I've pulled down the latest package and pasted in
John's sample code but 'log' tosses an unknown type error.
import com.blitzagency.xray.logger.XrayLog;
class EntryClass{
private var tfOutput:TextField;
private var mcScope:MovieClip;
function EntryClass(scope:MovieClip) {
log = new XrayLog(); //tosses error.
}
Other classes from the same folder structure _are being found but are
refusing to trace back statements (flashout's trace) placed in the
constructors. I _am able to navigate to the given .as file so why wouldn't
the compiler be able to find it?
I guess I'm looking for an overview of do's and don'ts regarding project
configuration (window platform) and can cause these sorts of niggles.
For example, do I have to use ASDT's New File/Folder creation method or can
I just put the files where I want them via Explorer and refresh the project.
When I try....stuff shows up but like I say...strangeness ensues.
When I add a linked folder to the src folder that points to c:\ClassPath
...that should make all those classes available, right? Again...I can
navigate the files but ...strangeness.
What's the secret behind enter a Classpath in the 'Properties | AS2
Classpath' box? When I enter 'C:\Classpath' (or c:/Classpath or
c:\classpathfinditdamnit) the dialog insists it doesn't exist.
If I try to import a class that doesn't exist shouldn't the compiler
complain?
Thnkx
--steve...
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
