Matt Keeter

Is this something that you could patch in a PR, so that it's fixed for other folks as well?

Thanks for the note; can you open a PR that adds this to the build instructions?

I'm curious whether we still need this workaround, or whether the `mingw-w64-x86_64-boost` recipe works out of the box at this point – it would be nice to remove the workaround...

`libfive` doesn't need Boost::Python, so I don't know 😆

Are you running on a high-DPI screen? It could be that I'm not setting all of the correct flags for correct behavior on Linux...

Pull requests are welcome; put it somewhere in `deploy/Linux`.

How's this?

You can do this easily with a custom script, e.g. ``` py title('data provider') input('width', float) input('height', float) input('depth', float) ``` Name the node `constants`, then refer to `constants.width`, etc....

This looks like a compiler issue, not an Antimony bug. Can you check that `g++` is also 4.9?

I'd like to hold this until keydown works, since it's unintuitive at the moment. I may poke at this myself, but no promises – feel free to investigate further if...