Nicholas Sharp

If you create a callback function, register it, and then `show()` in the usual fashion, on the first main loop iteration the callback will be invoked before the view data...

Two changes which will dramatically improve performance relating to geometric buffers (e.g. vertex positions). - Use a shared buffer on the GPU, instead of storing many redundant copies for each...

They don't currently appear in the docs.

e.g. set a known bounding-box. This should probably also be exposed in the UI somewhere. This is very necessary when crazy outliers can make the visualization useless.

For instance, http://polyscope.run/basics/parameters/#scaled-values. This should probably use `setPointRadius` in the example. Noticed via #62

Ensure all internal float types use double precision

1

General strategy is to use double types internally everywhere, to avoid subtle situations (like IO) where a loss of precision occurs in user data. We've been shuffling types internally, so...

Right now, there are lots of small bugs where changing some setting in the quantity option pane doesn't trigger a redraw when it should (e.g., changing bounds on colormap). This...