From the arcticDocument object you can request files to be loaded and you can access all files that previously been requested. The downloading of files occurs in the background so any call to the loadXXX functions will immediately return. You need add code to the file loaded events on the arcticShell object if you want to know when files have loaded.

For a lot of functions it is not necessary to have a loaded object. Most importantly, if you are initialising a script object with models, you may do so even if the model is not yet loaded. You can then monitor if the model instance has been created (as opposed to the modelFile object, these are very different). This is necessary if you need to do initialisations that require access to poses or groups.

The arcticDocument object is a global object. This is only relevant if you have multiple 3D windows on a single HTML page. In this case you will also see files appear that were requested in the other window.

Properties, Events and Methods

Name Type Description
loadAction MethodStarts an asynchronous download of an action file (.action)
actionFile loadAction(filePath as String)
loadChor MethodStarts an asynchronous download of an choreography file (.chor)
chorFile loadChor(filePath as String)
loadModel MethodStarts an async download of an action file (.model)
modelFile loadModel(filePathas String)
loadSound MethodStarts an async download of an action file (.wav or .mp3)
soundFile loadSound(filePathas String)
actionFiles PropertyactionFiles collection object containing all the actionFile objects
chorFiles PropertychorFiles collection object containing all the chorFile objects
modelFiles PropertymodelFiles collection object containing all the modelFile objects
soundFiles PropertysoundFiles collection object containing all the soundFile objects

 

©2000 arcticpigs. All rights reserved.
This is a draft version! The functionality of parts of the software are liable to change.