The Loader that is going to load this File.
The file type string for sorting within the Loader.
The key of the file within the loader.
An array of Files that make-up this MultiFile.
A reference to the Loaders baseURL at the time this MultiFile was created. Used to populate child-files.
The completion status of this MultiFile.
A storage container for transient data that the loading files need.
The number of files that failed to load.
Array of files that make up this MultiFile.
Unique cache key (unique within its file type)
A reference to the Loader that is going to load this file.
A reference to the Loaders path at the time this MultiFile was created. Used to populate child-files.
The number of files to load.
A reference to the Loaders prefix at the time this MultiFile was created. Used to populate child-files.
The current state of the file. One of the FILE_CONST values.
The file type string for sorting within the Loader.
Destroy this Multi File and any references it holds.
Checks if this MultiFile is ready to process its children or not.
Called by each File when it finishes loading.
The File that has completed processing.
Called by each File that fails to load.
The File that has failed to load.
Called once all children of this multi file have been added to their caches and is now ready for deletion from the Loader.
It will emit a filecomplete event from the LoaderPlugin.
A MultiFile is a special kind of parent that contains two, or more, Files as children and looks after the loading and processing of them all. It is commonly extended and used as a base class for file types such as AtlasJSON or BitmapFont.
You shouldn't create an instance of a MultiFile directly, but should extend it with your own class, setting a custom type and processing methods.