Anshul Singhvi

Hmm! Yeah that logic could probably be directly translated to Chairmarks somehow, probably by creating a new macro which stores an `Expr` object when run (the equivalent of `@benchmarkable`). It...

Nice! I agree the first one looks best.

That would be difficult to set with Documenter, because it creates a new module for every `@example` block. I do get the appeal of module-specific settings, though. How about this:...

You could, theoretically, roll your own `initialize_block!` method as in https://github.com/JuliaPlots/Makie.jl/blob/89da9ccc79b8422504f654d85019905a190b54c4/src/makielayout/blocks.jl#L288 and change it to not create a new `blockscene`. This might be a bit fragile depending on upstream changes,...

Another interesting thing would be backgrounds - as heatmaps or images for color gradients, for example. Also, is there any info on the placement of child Scenes within the main...

I think what you want here is something like CairoMakie's `[px/pt]_per_unit`, i.e., device scaling. My understanding is that this does not exist in GLMakie, since it is tightly integrated with...

Colorbuffer is a Makie function, so should work with whichever screen you send it - Cairo, GL or even WGL. It's technically part of the backend spec and returns a...

Those types are not in `using OrdinaryDiffEqCore` Or do you mean reexporting ADTypes from ODECore instead? Yeah as long as that's reexported here too, that works

It does!

So I tried to characterize this, here's what I did: ```julia using GLMakie depth_shift = Observable(1f-5) sph = Sphere(Point3f(0, 0, 0), 5) f = Figure() ax = Axis3(f[1, 1]; title...