undo on bones in pose mode selects all channels in graph editor
Open, NormalPublic

Description

System Information
WIn 8.1, gtx 970m

Blender Version
Broken: 2.79 e92f235283

Short description of error
undo on bones in pose mode selects all channels in graph editor
tested on 2.76-2.79 on several machines

Exact steps for others to reproduce the error
1 Add a single bone or rigifay metarig or any other rig.
2 Go to the Pose mode.
3 Insert any keyframes on 1st frame
4 Go any other frame.
5 move\rotate\scale bone
6 Insert keyframes
7 Go to the graph editor and toggle on Show_only_selected option. Also toggle on - only_selected_curves_keyframes
8 Select any channel in the list. Let it will be - Loc X or whatever. So the only Loc X f-curve highlighted. Only Loc X keyframes are visible.
9 move any keyframe on f-curve.
10 Press ctrl+Z for Undo.
11 Now, after undo all existing channels become selected so you can see all the f-curves with all keyframes on them. Which is incorrect.

There is no such problem in object mode. If you repeat these steps on cube then after undoing in graph editor the only selected channel stay highlited with only that f-curve keyframes visible.

Details

Type
Bug
Stanislav Ovcharov (Stan1) renamed this task from undo on bones in pose mode selects all channels in grapf editor to undo on bones in pose mode selects all channels in graph editor .
Stanislav Ovcharov (Stan1) updated the task description. (Show Details)
Sergey Sharybin (sergey) triaged this task as Normal priority.Dec 18 2017, 11:50 AM

@Stanislav Ovcharov (Stan1), this always helps a lot to attach simple .blend file, with as few steps as needed to reproduce the issue.

@Stanislav Ovcharov (Stan1), this always helps a lot to attach simple .blend file, with as few steps as needed to reproduce the issue.

did it -

  1. open it, move selected keyframe, press ctrl+z (all channeels become selected)
  2. select cube. move selected keyframe, press ctrl+z (only selected channel still selected)

this is kind of really annoying thing when you animate character) Is it impossible to fix it in 2.79b?

This is not a regression which is unlikely to have trivial fix. Such changes are not ending up in a corrective releases.

Currently working on undo code, if this is merged soon I can check on this issue.