Why is a Resize dialog more correct than a transform dialog? Both seems fine (not that Transform is not Translate).

You will change the size of the B-Bone profile. Try to change some values in the transform dialog. This doesn't work.

I'll take care of the graying out issue since that's my bad.

It looks like you can change the bbone scale using "Value X" in the redo panel. Which in turn will also update Y and Z, which you cannot change manually or individually... it's quite odd but it works.

When I was looking at the transform code, it all felt like a big mess. But I'm new to C so everything feels like a big mess to me, so I shouldn't be the judge of that. But if I'm right, maybe it could be thrown into a "code cleanup" task where we keep track of code that "works but isn't ideal". I don't know if such a thing already exists, I think it would be handy if it did.

In T68610#752171, @Demeter Dzadik (Mets) wrote:

I'll take care of the graying out issue since that's my bad.

Too late. Fixed that already in rB6e7ea807e1e.

It looks like you can change the bbone scale using "Value X" in the redo panel.

You can e.g. hit [ctrl-alt-s + x] and constrain the operator to resize in the x-axis . If you change the x-value in the redo panel, it resets the bbone profile from rectangle to sqare. It says ScaleB X, Y, Z in the upper left corner, so I think the resize dialog would be more appropriate here.

The redo panel is based on what operator was used last, so it would be a matter of moving that code to a different operator. The resize operator does something completely unrelated to things like bbone x/z width(which is only used for display), envelope head/tail radius and envelope distance. So maybe the answer is to give all these things their own operator? But would that make the transform code more or less of a mess?

I didn't know it was that complicated. Sounds like it's not worth fixing this.
In any case, you can now set the exact values in the bbone UI, thanks for cleaning that up!

Now, comparing the transform operations / dialogs in 2.7x and 2.8x, I think that the functionality in 2.7x was not broken from a user's perspective, even though it was strange. You could enable / disable the constraint axis in the UI, and then changing the "x-value" worked as expected.

For some reason, the dialog has been redesigned, so only the 'orient_axis' can be changed, which is in this case useless, and also the printed constraint_axis property seems to be ignored. Maybe someone could at least bring it into the old, messy but working state?

2.7x
bpy.ops.transform.transform(mode='BONE_SIZE', value=(5.86101, 12.911, 6.10101, 0.37), axis=(0, 0, 0), constraint_axis=(True, False, False), constraint_orientation='GLOBAL', mirror=False, proportional='DISABLED', proportional_edit_falloff='SMOOTH', proportional_size=1)

2.8x
bpy.ops.transform.transform(mode='BONE_SIZE', value=(0.973, 0.973, 0.973, 0), orient_axis='Z', orient_type='GLOBAL', orient_matrix=((1, 0, 0), (0, 1, 0), (0, 0, 1)), orient_matrix_type='GLOBAL', constraint_axis=(True, False, False), mirror=True, use_proportional_edit=False, proportional_edit_falloff='SMOOTH', proportional_size=1, use_proportional_connected=False, use_proportional_projected=False)