Tomasz Chabora

> Of course, removing the existing row-based animation functionality would be a bad idea for existing projects It would be bad in general, because with the current approach you can...

My "bad in general" refers to removing the existing functionality, not the one added in proposal. I only wrote it, because you said removing it would be bad for existing...

Anchor presets are set via internal `_set_anchors_layout_preset` method. Instead of hard-coding a specific property in the inspector, you can modify the setter to use `_edit_set_state()` when editor hint is active.

Some notes from testing: - enabling the Expose option will create 2 undo actions. You should make it single action (it can be achieved by nesting actions) - when you...

Tested this again (tbh I forgot I already tried it before) and most of the issues I listed were addressed. However: - I see the exposed node is still tied...

> ill move them back to being warning instead of the disabled color as i do think that makes more sense to the user. I also mentioned that the color...

I just found a major bug. Properties of exposed nodes are not saved. If you instance a scene with exposed node and modify the exposed node, the changes will be...

Well properties can be made uneditable in the inspector, but editors are a bigger problem. Currently there is no concept of readonly nodes for 2D and 3D editors. The closest...

> Wasn't sure if this override system bloated the PR too much beyond the scope of what I wanted to achieve. Some way to prevent data loss is required for...

Seems like overrides are working correctly, but they are stored twice for some reason: