-
-
Notifications
You must be signed in to change notification settings - Fork 291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bring back inline! :( #2353
bring back inline! :( #2353
Conversation
I guess we could also call it |
I don't want to rename it, since I really don't want to keep this solution in the future. Renaming the stopgap solution would be too much code churn for my taste ;) |
Yeah I figured, I agree |
Compile Times benchmarkNote, that these numbers may fluctuate on the CI servers, so take them with a grain of salt. All benchmark results are based on the mean time and negative percent mean faster than the base branch. Note, that GLMakie + WGLMakie run on an emulated GPU, so the runtime benchmark is much slower. Results are from running: using_time = @ctime using Backend
# Compile time
create_time = @ctime fig = scatter(1:4; color=1:4, colormap=:turbo, markersize=20, visible=true)
display_time = @ctime Makie.colorbuffer(display(fig))
# Runtime
create_time = @benchmark fig = scatter(1:4; color=1:4, colormap=:turbo, markersize=20, visible=true)
display_time = @benchmark Makie.colorbuffer(display(fig))
|
bring back inline :(
Guess we couldn't remove it yet, because I forgot the edge case of VSCode repl exposing a plotpane, but directly calling
display(eval_result)
, which madeMakie@0.18
always open a window, without a way to switch that behaviour.We really want a better solution, especially since
inline!(false)
doesn't currently always open a window, since we can't figure out how to always open a window, when VSCode thinks everything should go into the plotpane ;)Fixes #2331