-
-
Notifications
You must be signed in to change notification settings - Fork 308
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
Add origin to Transformation #4472
base: master
Are you sure you want to change the base?
Conversation
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(fig)
|
looking forward to this! one other suggestion in addition to the typos: i find the name |
I would prefer that I think, or maybe |
Having origin as an argument in rotate!() and scale!() was also my first thought but I think with how transformations work it's better to pull it out. Transformations don't consider the order you call things in. You're effectively setting or changing the state with I'd be fine with renaming the function. I also had |
Description
Related: #4445, #2637
This adds an
origin
toTransformation
so thatrotate!()
andscale!()
can be relative to something other thanVec3(0)
. It can be set withtranslate_origin!()
just liketranslate!()
.Example:
Type of change
Checklist