Search Issue Tracker
Fixed
Votes
0
Found in
4.5.0a3
Issue ID
581887
Regression
No
User should not be able to select "Delete" when the delete option is not supported
It should not be an option to select "Delete" when delete feature is not supported. If user by mistake has created a bunch of sliced sprites without noticing it, it is not possible to delete them from Assets folder (note, you need to delete the asset itself).
Prerequisite:
You need a sprite in you assets
Repro:
1. Select the Sprite from the asset
2. In the Inspector, select Sprite mode > multiple
3. Select Sprite Editor
4. In the sprite edito create, by slicing, a boundle of new "sub" assets
5. Navigate to the asset folder and select the bundle of "sub" assets" and right click
5. select Delete
Result: Nothing happens
Expected result If it is not possible to delete the "sub"assets, then Delete should not be an option
Note: By selecting the asset it self (the top level), it can be delete
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment