Butttons for Keyframing Settings Are Mutually Exclusive #43343

New Issue

Sam Brubaker · 2015-01-21T17:46:40+01:00

Sam Brubaker commented

2015-01-21 17:46:40 +01:00

Version 2.73 (Linux 64-bit)

This bug requires no example file to reproduce.

How to reproduce:

Open Blender, go to the Scene Properties, and add a Keying Set.
Examine the "Keyframing Settings" for the keying set and notice what happens when you click them.

Turning on one option disables the others, which might lead a user to think that these three miscellaneous options are related, but they are not. Enabling more than one option in this panel requires the user to hold down shift while clicking. This makes no sense and no other area in the properties window behaves like this!

I think this design flaw counts as a bug. These options should not be grouped this way, and ought to be in the form of checkboxes instead.

Version 2.73 (Linux 64-bit) This bug requires no example file to reproduce. How to reproduce: - Open Blender, go to the Scene Properties, and add a Keying Set. - Examine the "Keyframing Settings" for the keying set and notice what happens when you click them. ![KeyframingSettings.png](https://archive.blender.org/developer/F138596/KeyframingSettings.png) Turning on one option disables the others, which might lead a user to think that these three miscellaneous options are related, but they are not. Enabling more than one option in this panel requires the user to hold down shift while clicking. This makes no sense and no other area in the properties window behaves like this! I think this design flaw counts as a bug. These options should not be grouped this way, and ought to be in the form of checkboxes instead.

Sam Brubaker commented

2015-01-21 17:46:40 +01:00

Changed status to: 'Open'

Sam Brubaker commented

2015-01-21 17:46:40 +01:00

Added subscriber: @rocketman

Joshua Leung self-assigned this 2015-01-22 12:17:02 +01:00

Joshua Leung commented

2015-01-22 12:17:02 +01:00

Assigning to self. I've been annoyed about this for a while now.

IIRC, at the very beginning, a very long time ago, it wasn't like this. Then, it suddenly changed once, when someone used the enum bitflag prop-widget and/or wrapped all of them in that way... which is incorrect of course.

Then there's the side issue that even if these buttons look ok, they don't actually completely function in the intended way: that is, it was intended that you could use these to override the defaults, but that doesn't work atm.

Assigning to self. I've been annoyed about this for a while now. IIRC, at the very beginning, a very long time ago, it wasn't like this. Then, it suddenly changed once, when someone used the enum bitflag prop-widget and/or wrapped all of them in that way... which is incorrect of course. Then there's the side issue that even if these buttons look ok, they don't actually completely function in the intended way: that is, it was intended that you could use these to override the defaults, but that doesn't work atm.

Joshua Leung commented

2015-01-25 11:59:16 +01:00

An update:
So, I've found the commit responsible for this now. It is 1c3f2354f8

Working on rolling back some of these things now :)

An update: So, I've found the commit responsible for this now. It is 1c3f2354f8 Working on rolling back some of these things now :)

Sam Brubaker commented

2015-01-25 17:39:25 +01:00

Thank you, aligorith!