Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inspector keeps deleted asset displayed #42295

Open
Flavelius opened this issue Sep 24, 2020 · 2 comments
Open

Inspector keeps deleted asset displayed #42295

Flavelius opened this issue Sep 24, 2020 · 2 comments

Comments

@Flavelius
Copy link
Contributor

Godot version:

3.2.3.stable.mono.official

OS/device including version:

Windows 10 x64

Issue description:

As the title states, the inspector still displays deleted assets after they should have gone.
See: https://streamable.com/uywpuf

Steps to reproduce:
Double click an asset (material for example) so it is displayed in the inspector, then delete it. See the inspector still diplay it.

@Calinou
Copy link
Member

Calinou commented Sep 24, 2020

See also godotengine/godot-proposals#1550, which is the same issue but for scripts.

The current behavior may be considered intended. Maybe you didn't actually want to remove the resource and want to save it to recover it.

@Flavelius
Copy link
Contributor Author

There's already a confirmation dialog for deleting assets (which is also more than unity even does to help with that and even there it's not needed). If one really doesn't want to delete an asset clicking cancel is the naturally best option.
Normally when editing an asset the changes are directly persisted and in this case my intuitive expectation would be that editing the fields now throws errors etc because the file just vanished behind the scenes. And this expectation (or the lack of the expected result too) makes it feel buggy/unintended. So it's probably more a case of look&feel, but maybe this can be given another thought when that side of the development becomes focus again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants