(Clojurescript) accidental munging of elapsed sensor

In both of those cases, I start by invoking the control module's create_elapsed_sensor function, and what it returns is an object with all its attributes munged.

Now, Clojurescript uses Google Closure (like b4w) to compile into Javascript. So I suspect the problem is how I declared Clojurescript's b4w externs. But before I start altering the externs, I want to make sure I'm not doing some other blend4web-specific mistake.

Hi, Mike!
This is normal, it looks the same as in compiled b4w.min.js. I don't see a problem here.

Yes, you should declare b4w-specific externs to avoid possible bugs. Firstly, here you can find the list of the externs that we use for compilation: source.

Besides them, we also generate a special temporary file during the compilation, which contains some data gathered from the source files: source. We find API functions/variables declared as "exports.IDENTIFIER" and also indetifiers under the @cc_externs token. You can see it here: source.

It turns out I'm a goddamn fool – I was trying to create the manifold from the elapsed sensor object, *not* from the controls module :P

I've managed to cobble together a basic scene – some animation, manipulating a simple cube via clojurescript. Check it out here

Here's that same project's source code – you can find the 'meat' of the logic in ../src/cube_test/core.cljs.

Note that it seems to work better on Chrome – FF doesn't seem to load shadows the same way.

Hmm… I don't see the difference. Can you show a screenshot?

But I'm confused on how to use it – would I invoke this in my elapsed sensor callback? Or do I invoke it somewhere else?

var cb = function(value) {
    var cube = m_scenes.get_object_by_name("Cube");
    m_trans.set_translation(cube, 0, 0, value);
}

m_time.animate(-5, 5, 10000, cb);