We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In GitLab by @tjlaboss on May 25, 2022, 11:25
Requires #32.
Once it is easy to shift a surface in x, y, z:
a numbered object collection like 'pz', 'c_z', etc. could be made, and called something like 'shiftable_z' or whatever.
Then a user can say for surf in problem.shiftable_z: surf.do_thing(dz)
for surf in problem.shiftable_z: surf.do_thing(dz)
The text was updated successfully, but these errors were encountered:
I like it. Not sure I like the name though.
Probably would need to make a new generator object.
Question: if there's a surface that we know should support this sort of translation but doesn't, should that raise an error?
Sorry, something went wrong.
In GitLab by @tjlaboss on May 25, 2022, 11:59
Yes, a NotImplementedError
NotImplementedError
tjlaboss
No branches or pull requests
In GitLab by @tjlaboss on May 25, 2022, 11:25
Requires #32.
Once it is easy to shift a surface in x, y, z:
a numbered object collection like 'pz', 'c_z', etc. could be made, and called something like 'shiftable_z' or whatever.
Then a user can say
for surf in problem.shiftable_z: surf.do_thing(dz)
The text was updated successfully, but these errors were encountered: