You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The restart prompt for unsaved resources shows even in an empty project with no open scenes:
This is a regression from #102017, as this dialog wasn't present before. It can be confusing to see this dialog if there's nothing that can be saved, since the user might think they have unsaved resources when they don't.
Steps to reproduce
Create a new project and open it in the editor.
Do not create or open any scenes/resources.
Change a setting that requires a restart, then click the Save & Restart button.
A restart dialog shows up, but choosing Don't save or Save & Reload will do the same thing as there is nothing to save.
Minimal reproduction project (MRP)
N/A
The text was updated successfully, but these errors were encountered:
Changing project/editor settings marks global history as unsaved. There is no way to differentiate that from actual resource modifiactions and the dialog is somewhat expected in this case.
Not sure if such list is even available. Also the editor only checks whether the undo history is "unsaved" (i.e. it has actions performed since the last save), so they'd need to be checked too.
Tested versions
System information
Godot v4.4.rc (3ef055f) - Fedora Linux 41 (KDE Plasma) on X11 - X11 display driver, Multi-window, 1 monitor - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4090 (nvidia; 565.77) - 13th Gen Intel(R) Core(TM) i9-13900K (32 threads)
Issue description
The restart prompt for unsaved resources shows even in an empty project with no open scenes:
This is a regression from #102017, as this dialog wasn't present before. It can be confusing to see this dialog if there's nothing that can be saved, since the user might think they have unsaved resources when they don't.
Steps to reproduce
Minimal reproduction project (MRP)
N/A
The text was updated successfully, but these errors were encountered: