Add a button to set all linked properties in the inspector

[Kartopod]

There are a lot of instances in the editor inspector where there are linked properties whose values you want to set to the same value. At the moment, since they're separate properties, setting them all to the same value individually is very cumbersome.

For example: In a StyleBoxFlat, there are the Border Width, Corner Radius, Expand Margin and Content Margin properties.

Of course, it still makes sense that they should be separate properties, because sometimes you do indeed want to have different values for them, but an input field (Or a button that pops up an input field) to set all the values of a linked property at once would greatly improve the user experience.

[aXu-AP]

Agree, this would be a good QoL improvement. Such thing exists for scale, so it should look similiar:

Another area which would benefit from this: RichTextLabel's font sizes:

[tetrapod00]

Yeah, I've been wanting something like this for a while now. I agree this is a good default UI to match current behavior in the editor.

The VectorN linking is implemented here, and in the rest of this file. But that linking only deals with the subproperties of a single property. Doing something similar for multiple properties would have to reimplement similar code elsewhere.

https://github.com/godotengine/godot/blob/97ef3c837263099faf02d8ebafd6c77c94d2aaba/editor/editor_properties_vector.cpp#L236L242

[Mickeon]

I've always had the idea that you should be able to select multiple properties/spin sliders in the Inspector by holding CTRL, but in practice I'm not sure how complex that would be.

[Kartopod]

@Mickeon Blender's UX for this is extremely good:

• Dragging vertically allows selection of multiple fields, after the first horizontal dragging is detected, vertical selection is locked.
• You can also drag on only a few fields.
• Dragging fields that have different values selects and sets them to the value you started dragging from.
• 'Selecting' fields allows you to manually input the same value to multiple fields.
  

[aXu-AP]

There's a few things I don't particularly like in Blender's approach:

• It's easy to accidentally move mouse horizontally before you reach all the fields (could be fixed with bigger margins).
• You can select only neighboring elements.

Overall it does feel good and I do use it in Blender. But I like @Mickeon 's suggestion better (it's also likely easier to implement).

[Kartopod]

That's fair. Just to throw around my thoughts aswell, I love how effortless it is to drag over all the fields and affect them at once. Pecking and choosing like how @Mickeon suggested would definitely help make the UX better than what it is now, but I feel like there would still be some friction when you want to set all the values together.

This is especially the case with the theme properties (eg: Corner Radius) because 90% of the time you want to quickly set all four of them to the same value. Having to click each one (imo) would still be very slow.

[aXu-AP]

If we implemented multiselect, shift clicking to choose consecutive properties should also work.

[Kartopod]

I suppose a good middle ground for that would be to allow shift clicking, as well as shift click + dragging. This would let you peck and choose individual elements, as well as select neighbouring elements quickly

[michaelharmonart]

just a note, maya has a system very similar to blender where you can drag and select multiple channels in the channel box and then you can adjust them by then middle mouse dragging left and rightAnywhere to adjust them.

Animators love this and It's one of the first tools you're taught for animation in maya. Just to throw it in as another possibility. It avoids the accidental adjustment that's possible in the blender style.

[AndreyCortez]

For me at least, I think a very intuitive way of doing this would selecting the fields like you select files on the file syetem explorer. Pressing control you can select one by one, pressing shift you select them from top to bottom. Something like this but a check would be needed to see if the types are the same.

[kaiiboraka]

One simple solution to changing ALL values that I've thought of in the past is an additional "All" field, that would be editable even from collapse. Attached is a simplified mockup. Changing this value would automatically change each subvalue to match.

Ctrl+Click still has merit for choosing any arbitrary number of fields less than the max, so I'm still a fan of that solution in addition. But this would be a nice first step to solve the problem of laborious multi-selection when you simply want to change them all.

[aXu-AP]

This idea could be nice on some curated cases (like the ones demonstrated). Not everywhere though, that would add clutter and be sometimes nonsensical...