8000 Keep rotation center · Issue #70 · dalboris/vpaint · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Keep rotation center #70

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.

Sign up for GitHub

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

Jump to bottom
Open
algorev opened this issue Nov 25, 2016 · 3 comments
Open

Keep rotation center #70

algorev opened this issue Nov 25, 2016 · 3 comments
Labels
feature request

Comments

@algorev
Copy link
algorev commented Nov 25, 2016 •
edited
Loading

The rotation center should be kept between two operations on an edge, as it would be more practical for rigging, etc.
@dalboris
Copy link
Owner

Yes that could be useful, though we will have to carefully think about how exactly to achieve this. Random thoughts to think about:

  • Should they be preserved only during a given VPaint session, or across sessions (i.e., is it saved in the .vec file?). If it is for rigging, then across sessions of course.
  • Are there use cases where preserving this rotation center would be undesirable/irritating? (I think yes)
  • Should the behavior "preserve vs. non-preserve" be a user preference?
  • Should the behavior "preserve during session vs. preserve across sessions" be a user preference?
  • Should this choice of behavior be per-edge/face?
  • What about a selection of multiple edges/faces?

At a higher-level, I feel that if the use case is for rigging, then maybe this functionality should be provided per-group/layers, once groups/layers are implemented. It would probably a better way to achieve the same functionality. Or or course, skeletons (#71) are the most natural choice to achieve this functionality.

@algorev
Copy link
Author
algorev commented Dec 1, 2016

Yes, maybe you're right. I think #71 supersedes this. Shall we close this issue?

@dalboris
Copy link
Owner
dalboris commented Dec 1, 2016

No, let's leave it open for now, skeletons won't be implemented any time soon, and we need to some up with a reasonable solution for this functionality in the meantime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dalboris @algorev
0