New Features (since Beta)

• Now supports Mac OS X
• New method: moka_GetLastJavaException() returns the last exception thrown from the JVM
• New method: moka_GetCurrentJVMInstalled() replaces GetInstalledJVMs(). The new method returns a string that contains the current default JVM installed on the user's computer, or the version of the JVM delivered with the Director projector. See the User Manual
• New method: moka_Path(). When passing an absolute path as a parameter to a Java class, this method ensures that the path is correctly formatted for the end-user's OS.
  All Moka Xtra method names have been prefixed with "moka_" for easier identification in your Lingo code
• Two new sample movies(Zip and UnZip Utilities) have been added to the Demos page

Bug Fixes
A memory leak was noticed in version 1.1.0 and occurred on all platforms [fixed]

Known Limitations

• Only one instance of the JVM is created. Once the JVM is started, by instantiating Moka Xtra, the only way to destroy its instance is by closing Director. Therefore, if you are modifying your Java™ classes at authoring time, you must close and restart Director in order for the changes to take effect
• On Mac OS 8 & 9, you have to restart Director (to re-instantiate the JVM) each time the Class Path is changed, in order for the new path to take effect. Please view the knowledge base article entitled: Recommended practice for working with multiple class paths
• To make a cross-platform application that runs on Mac OS 8 or 9, you should only use classes found in Java™ Platform 1.1 API, in addition to your own custom classes (any custom classes used should be based on this version of Java™)
  For a complete listing of the classes available in Java™ Platform 1.1 API, go to Sun's website