Hey hey :)

Looks super interesting to me, I can see the usefulness in specific cases. I'd be interested in hearing @Demeter Dzadik (Mets)'s thoughts on this.

I read the description and opened the updated example file... but I'm honestly still a bit confused about what exactly is being talked about here. In the example file the text reads "Rotate the stuff that has Emties (not the Emties themselves" and I'm not sure what "stuff" is being referenced, nor how it does something wrong or right. Perhaps I haven't had enough coffee this morning.

Looks very interesting to me, can easily see it being very useful! :)

Can we have this be a setting in the preferences?

In D5875#135739, @Wayne Dixon (waylow) wrote:

Although I did find in interesting that in Hjalti's analogy about learning photography he mentioned that if someone was serious about learning, they should change all the settings to manual. Which is in fact making the user change away from the default factory settings. That is the opposite of what he was trying to argue...unless Hjalti's vote was to actually make the default key type constant, which it might just be ;P

I've read all the comments and have given this some thought. I can see why this can be a helpful tool but also where it may be counter-productive.

This feature is creating massive headaches for me. (I'm a right click-select user by the way)

Sorry, I didn't see the notification so I'm a bit late to the game...

I would not have this be a global toggle, this is a very specific view related thing. Users might want to work with these things enabled in the dopesheet but not in the graph editor and vice versa.

This seems to be a feature that was made for a reason but I can't for the life of me come up with a scenario where it's useful.

In rB6491d50d02b7c93b4955fe05dae62930f3a76ce1#206746, @Brecht Van Lommel (brecht) wrote:

@Hjalti Hjálmarsson (hjalti), when you use the G key for global transforms, is that for rotation, translation, or both?

I'm sure this will just be lost in the echo chamber but here's at least an animator's viewpoint on this thing:

What the... after restarting Blender I'm utterly unable to reproduce the bug... gonna continue to work as normal as seen if it pops up again today (then at least I can figure out in what scenario it happens)

Will this be optional? Will I be able to toggle this on/off?

PS. When you delete a path it doesn't go away but rather stays there until you refresh the rig by moving a bone.

I wonder if @Campbell Barton (campbellbarton) may have already looked at this and addressed it, because it used to be a 100% consistent crash but now it works fine.

Correction, this bug only pops up when the "Only Insert Available" is checkmarked in the user preferences.