Justin-Fisher

Here's some Python code that performs the recursive search I'm talking about (taking an API Node and a defName as input), though I'm sure my list of searchable_field types is...

If it were possible, my inclination would be to instead move in the direction of letting `scale` work meaningfully with more things, rather than reducing the number of things that...

**Edit: For anyone arriving here late who doesn't want to scroll down through what has now become a great wall of text, here is a link to my current draft...

Also, is the roundabout import into Python using `ROTATIONAL = ctypes.c_int.in_dll(_wb, 'wb_ROTATIONAL').value` really necessary? I was under the (perhaps mistaken) impression that for vanilla types like ints, `ROTATIONAL = _wb.wb_ROTATIONAL`...

> I believe both versions are needed. the `wb_` version is a symbol (similar to API function which starts with `wb_`) whereas the `WB_` version is an enum (similar to...

The more explicit type conversion like that we have to do, the more annoying it will be to write the Python controller manually, though I can probably jerry-rig a system...

So I've extracted all the constants from the Matlab controller, and I've gone through all the constants that were used in the swig-produced `controller.py`, and worked out systematic ways to...

Yes, much of the automated name-translation system I came up with was translating between the Matlab/C naming system that keeps everything at global scope, and the swig naming system which...

Ok, I have compared the constant values produced by the swig/C++ controller to the corresponding constant values produced by the Matlab controller. The good news is that most of these...

Edit: I've now added to this branch a simple module `WB_CONSTANTS.py` that defines all the constants to their currently-correct values using their documented C names, except with a leading underscore...