When the inspector is empty, opening the "extra resource options" menu
produces a error:
> Condition "current_res.is_null()" is true.
Opening the mneu with no current resource is valid use case, so
`ERR_FAIL_COND` should not be used.
(cherry picked from commit cb0fa0ed7b)
Also don't prompt users to delete the project folder for now.
This is a temporary fix to ensure that users do not delete their entire home folders by mistake
(cherry picked from commit 45a26ff292)
dock->get_index() on line 4463 was not behaving as expected
due to dock having an internal sibling, so now we just get the
index excluding internal nodes.
line 4742 would throw an error if you made multiple docks
floating then redocked the end docks first, but no longer
(cherry picked from commit 21578e0bb4)
This quotes the executable name so that copying it always works
(even if the path contains spaces).
The command is also indented from the rest of the text and is
no longer single-quoted, as that can prevent the command from
running if the line is copied in its entirety (with the quotes).
(cherry picked from commit ddc9cc3e49)
This fixes a bug introduced by 806425621c, where dragging the gizmo no longer respected local transforms.
I'm not sure why I called set_local_coords_enabled(false) in _compute_edit. Removing this line seems to fix gizmo-dragging local transforms, without breaking anything else.
I also noticed that confirming a transform leaves the gizmo axis lines on the screen. This is fixed by calling update_transform_gizmo after clearing the edit mode/instant flags, so update_transform_gizmo knows not to render any axes.
(cherry picked from commit d3d1223b97)
If calling set_mesh with a PrimitiveMesh that has pending update, the
_mesh_changed function would be called twice. The first time before
set_base had been called, which could lead to an ERROR message about
trying to set an invalid surface override material.
(cherry picked from commit 007b488a5c)
Having local_space enabled when starting a transform changed the
behavior of VIEW space transforms. Now we disable local_space when
starting a blender transform (there was already logic to restore the
setting after the transform ends).
This also hides the gizmo while performing a blender transform,
otherwise the user will see it snap back and forth between the local and
global alignment. I think the transform looks cleaner with the gizmo
hidden anyways.
Fixes#59392.
(cherry picked from commit 806425621c)