Oolite Bulletins

• Stack traces now include the names and values of variables for each frame. (Specifically, it lists this, then any function parameters, then any local variables.)
• The logcontrol.plist entries for controlling stack traces have been removed. Instead, when the debug console is connected, they can be controlled with the properties debugConsole.dumpStackForErrors and debugConsole.dumpStackForWarnings (default: true; changes are persisted in preferences). Without the debug console, stack traces are not dumped by default but can be enabled with the  hidden settings “dump-stack-for-errors” and “dump-stack-for-warnings”.
• When the debug console is connected, a stack trace can be dumped at any time with the debugger; statement. Without the debug console, this does nothing and takes essentially zero time.
• Stack traces are always dumped when the time limiter kills a script.

this.name = "debuggerTest";
this.version = "1.0";

this.shipWillLaunchFromStation = function shipWillLaunchFromStation(station)
{
    function doStuff()
    {
        var somethingStrangeHappened = (station == system.mainStation);
        if (somethingStrangeHappened)
        {
            log("debuggerTest.strangeness", "Something strange happened!");
            debugger;
        }
    }
    
    doStuff();
}

[debuggerTest.strangeness]: Something strange happened!
[script.javaScript.debugger]: debugger invoked during debuggerTest 1.0:
[script.javaScript.stackTrace]:  0 /Users/jayton/Library/Application Support/Oolite/AddOns/script.js:12 doStuff()
[script.javaScript.stackTrace]:     this: [object Global]
[script.javaScript.stackTrace]:     somethingStrangeHappened: true
[script.javaScript.stackTrace]:  1 /Users/jayton/Library/Application Support/Oolite/AddOns/script.js:16 shipWillLaunchFromStation()
[script.javaScript.stackTrace]:     this: [Script "debuggerTest" version 1.0]
[script.javaScript.stackTrace]:     station: [Station "Coriolis Station" "Coriolis Station" position: (-49515.3, 60769.4, 427622) scanClass: CLASS_STATION status: STATUS_ACTIVE]
[script.javaScript.stackTrace]:     doStuff: function doStuff

• The new JS engine (which excludes normal svn builds for Linux, but not nightlies)
• Native Objective-C exceptions (which excludes Windows, at least with the toolchain another_commander is using)
• SpiderMonkey must be built with MOZ_TRACE_JSCALLS defined (which probably excludes Linux nightlies, but should be fixable).

                                                        NAME  T  COUNT    TOTAL     SELF  TOTAL%   SELF%  SELFMAX
                    (oolite-nova-mission.js:173) <anonymous>  J      1     0.11     0.09    41.2    31.9     0.09

console.trace(function test() {
    function inner (scale) {
        var v = new Vector3D(-1, 2, 0);
        return v.multiply(scale);
    }
    return inner(Math.random());
})

>>>> Beginning trace.
  >> (<console input>) test(this: [Script "oolite-debug-console" version 1.75]) [JS]
    >> random() [NW]
    >> (<console input>) inner(this: [object Global], scale: 0.012386843307234607) [JS]
      >> VectorConstruct [ON]
        >> VectorFromArgumentListNoErrorInternal [ON]
      >> multiply() [NW]
        >> VectorMultiply [ON]
          >> JSObjectGetVector [ON]
          >> OOJSArgumentListGetNumberNoError [ON]
          >> VectorToJSValue [ON]
            >> JSVectorWithVector [ON]
<<<< End of trace.

• [JS] entries are pure JavaScript function calls; there’s one for test and one for inner, with this and arguments listed. As in the trace results, these have a location; code from the console is now tagged “<console input>” instead of “oolite-debug-console.js:779”.
• [NW] entries are “native wrappers”, the JavaScript representation of functions implemented by Oolite or SpiderMonkey. In this example, there’s one for random (i.e. Math.random()) and one for multiply (i.e. Vector3D.prototype.multiply()).
• [ON] entries are Oolite native functions with profiling support.

• New mission.runScreen() parameter spinModel (boolean, default true). If false (or a falsey value), and model is specified, the model will not be rotated automatically (it will be created with orientation (1/√2, 1/√2, 0, 0), which shows it from the top with the front towards the top of the screen).
• New property mission.displayModel (Ship); while a mission screen is running, if it has a model, this is it.
• system.allShips no longer includes ships with status STATUS_COCKPIT_DISPLAY (the fact that they’re technically “in the universe” is an implementation detail that wasn’t meant to be exposed; system.filteredEntities() always filtered them out). Cabal Common Functions’ entGetScreenModel() relied on this bug, so it will no longer work. Use mission.displayModel instead. (I assume Cabal Common Functions will be updated to do this in 1.75.)

Svengali wrote:

Oh, I guess you mean mission.displayModel right?

(function () {
const escortPositions =
[
    // V-shape escort pattern
    new Vector3D(-2, 0, -1),
    new Vector3D( 2, 0, -1),
    new Vector3D(-3, 0, -3),
    new Vector3D( 3, 0, -3)

/*
    // X-shape escort pattern
    new Vector3D(-2, 0,  2),
    new Vector3D( 2, 0,  2),
    new Vector3D(-3, 0, -3),
    new Vector3D( 3, 0, -3)
*/
];

this.coordinatesForEscortPosition = function (index)
{
    var highPart = 1 + (index >> 2);  // Equivalent to 1 + Math.floor(position / 4)
    var lowPart = index % 4;
    
    var spacing = this.ship.collisionRadius * 3 * highPart;
    
    return escortPositions[lowPart].multiply(spacing);
}
}).call(this);

• A higher-resolution version of your current background/overlay, with the same margins: use the dimensions of the old versions. For a full-screen backdrop, this will generally be width = 1024, height = 512 (or just height = 512).
• A proportionately scaled-up version of your current background/overlay with the margins trimmed: height = 480.
• An image scaled disproportionately to fit into a power-of-two aspect ratio (this is fiddly, but makes the best use of memory): the ideal dimensions of the image, scaled to a height of 480. For instance, for a 4:3 image, you’d use width = 640, height = 480. In this case, both dimensions must be specified.

• screenbackgrounds.plist
• [url=http://wiki.alioth.net/index.php/Oolite_JavaScript_Reference:_Mission#runScreen]mission.runScreen()[/url]
• setScreenBackground() and setScreenOverlay().