Show poselib content in outliner, apply function #23306

New Issue

Torsten Rupp · 2010-08-14T07:09:20+02:00

Torsten Rupp commented

2010-08-14 07:09:20 +02:00

%%%This patch improve patch #22805: "Show poselib content in outliner" by now also adding an "apply" function in the context menu in the outliner overview for the poselib content (open context menu in outliner with right mouse button).

The outliner show the poselib content like this:

when closed:

Armature

+ PoseLib

when opened:

Armature
- PoseLib
  - pose name 1
  - pose name 2
  - pose name 3

...

A pose can be selected in the list and then applied to the current frame with the new "apply" function from the context menu. Context menu look like this:

+----------------------------+

Outliner PoseLib Operation
Unlink
Apply
+----------------------------+

BTW: the existing functions for browsing and modifying the poselib are not changed and can still be used.

It would be nice if someone may review the patch. I'm looking also forward to see the patch pushed into the repository.
%%%

%%%This patch improve patch #22805: "Show poselib content in outliner" by now also adding an "apply" function in the context menu in the outliner overview for the poselib content (open context menu in outliner with right mouse button). The outliner show the poselib content like this: when closed: - Armature ``` + PoseLib ``` when opened: - Armature - PoseLib * pose name 1 * pose name 2 * pose name 3 ``` ... ``` A pose can be selected in the list and then applied to the current frame with the new "apply" function from the context menu. Context menu look like this: +----------------------------+ | Outliner PoseLib Operation | | -- | | Unlink | | Apply | +----------------------------+ BTW: the existing functions for browsing and modifying the poselib are not changed and can still be used. It would be nice if someone may review the patch. I'm looking also forward to see the patch pushed into the repository. %%%

Torsten Rupp commented

2010-08-14 07:09:20 +02:00

Changed status to: 'Open'

Torsten Rupp commented

2010-11-08 08:09:03 +01:00

%%%update patch to r32936
%%%

%%%update patch to r32936 %%%

Torsten Rupp commented

2011-01-06 05:33:27 +01:00

%%%update r34026%%%

Torsten Rupp commented

2011-07-03 13:58:44 +02:00

%%%updated to r37993
%%%

%%%updated to r37993 %%%

Yousef Harfoush commented

2011-11-29 17:11:13 +01:00

%%%can you update to recent trunk, as there are a lot of functionality change, thank you.%%%

Torsten Rupp commented

2011-12-03 12:35:34 +01:00

%%%I will update the patch to the recent revision in trunk.
%%%

%%%I will update the patch to the recent revision in trunk. %%%

Torsten Rupp commented

2011-12-06 04:27:18 +01:00

%%%I updated the patch to recent trunk, r42450.

I'm looking forward to see the patch integrated.
%%%

%%%I updated the patch to recent trunk, r42450. I'm looking forward to see the patch integrated. %%%

Joshua Leung commented

2012-01-22 12:13:06 +01:00

%%%Hi,

Just a quick review:
I'm not so keen on duplicating the code used to actually manipulate Pose Library data between two places, and especially in the Outliner code.

A better approach may be to separate out some of these core operations from the Pose Library operators, making ED_* api calls for them in poselib.c and exposing for use in Outliner (as well as for the operators). Certainly this would be closer in spirit to the original design of the code back in 2.4 when there were no operators, and the current operators were defined as API calls which could be used from various event handlers.

It may also be useful to look at integrating other functionality, such as deleting and renaming poses from here.

Cheers%%%

%%%Hi, Just a quick review: I'm not so keen on duplicating the code used to actually manipulate Pose Library data between two places, and especially in the Outliner code. A better approach may be to separate out some of these core operations from the Pose Library operators, making ED_* api calls for them in poselib.c and exposing for use in Outliner (as well as for the operators). Certainly this would be closer in spirit to the original design of the code back in 2.4 when there were no operators, and the current operators were defined as API calls which could be used from various event handlers. It may also be useful to look at integrating other functionality, such as deleting and renaming poses from here. Cheers%%%

Bastien Montagne commented

2014-08-07 15:22:29 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2014-08-07 15:22:29 +02:00

Bastien Montagne commented

2014-08-07 15:22:29 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2014-08-07 15:22:29 +02:00

Sounds time to archive.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Show poselib content in outliner, apply function #23306