Constructor
Returns the date and time this version of EnvisionWeb was built
Returns the version of CEETRON Envision for Web
Format: Major.Minor.Patch-Build. E.g. '1.2.0+34145A' or '1.2.0-rc1++38C14A
Returns the number of viewers in the client application.
Manually add a model to the set of models that need background processing
Adds a new Viewer to the session.
The Viewer is tied to a HTML Canvas element, and the provided canvas must be capable of rendering WebGL. A Viewer can have many Views, and all the Views within a Viewer can share WebGL resources. So, to show the same Model in two Views, using one Viewer with two Views is more efficient than using two Viewers with one View each.
A client application can contain many Viewers, but each Viewer must be linked to single unique Canvas.
Deletes all viewers from the app.
Deletes the viewer at the given index.
The index must be zero based and between 0 and viewerCount - 1
Destroys the session object. This will delete all the viewers.
Returns a read only array with all viewers in the session
Returns the viewer with the given index.
The index must be zero based and between 0 and viewerCount - 1
Mandatory update method for the CEETRON Envision Client.
This method must be called from a requestAnimationFrame() for animations to run and server communication to work as expected.
The standard code for doing this is:
// Setup timer to keep the session viewer up-to-date
function myAnimationFrameCallback(highResTimestamp) {
mySession.handleAnimationFrameCallback(highResTimestamp);
requestAnimationFrame(myAnimationFrameCallback);
}
requestAnimationFrame(myAnimationFrameCallback);Remove a model that was previously added manually to the processing set
Generated using TypeDoc
The CloudSession's responsibility is to manage the Viewers and the main event loop of EnvisionWeb (handleAnimationFrameCallback).
All EnvisionWeb applications need a CloudSession object. There is only need for one, even in apps with multiple viewers, views, models and remote servers.