Add docs for how object's stored transforms work #23
No reviewers
Labels
No Label
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-developer-docs#23
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "nathanvegdahl/blender-developer-docs:stored_object_transforms"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The main point is to document how loc/rot/scale interact with
dloc/drot/dscale. But this also covers the parent-inverse matrix.
My main questions:
Nice to have documentation like this! Two thoughts:
That's fair, yeah. In this case, I documented it because that specific question came up when we were trying to make a related decision, and it ended up being a bit annoying to track down. But the main challenge was finding the relevant functions. So I can just summarize "the components are combined individually before being assembled into a matrix" and then point to the relevant functions for when more details are needed.
Oh! I didn't realize that. For prose I personally find that hard wrapping actually makes editing harder, since I always edit prose with word wrapping on anyway. And hard wrapping just means I have to take the extra step to re-wrap things after I've made edits. But if that's already been decided, I'm happy to adhere.
Thanks, sounds great!
Yeah, it's not easier for me either TBH. But it's nice to be consistent.
We indeed use a 100 character (actually 99) limit, see style guide. It seems like people expect a line limit, it kept coming up as question. Maybe relying on editor line wrapping is fine, but I'd hope that auto-formatting takes away any effort either way. That's why we have the
.editorconfig
in place now.I've addressed the comments now.
Note that I wrapped to less than 100 characters for consistency, since the rest of this file does as well. (I somehow just didn't notice that it was hard wrapped at all before.)
Not relevant to this PR, but the official EditorConfig extension for VSCode doesn't appear to support the
max_line_length
config option, which is annoying.Would be nice to add this to the docs!