36cfb2170f
# Objective fix #12344 ## Solution use existing machinery in track_assets to determine if the asset is unused before firing Asset::Unused event ~~most extract functions use `AssetEvent::Removed` to schedule deletion of render world resources. `RenderAssetPlugin` was using `AssetEvent::Unused` instead. `Unused` fires when the last strong handle is dropped, even if a new one is created. `Removed` only fires when a new one is not created. as far as i can see, `Unused` is the same as `Removed` except for this "feature", and that it also fires early if all handles for a loading asset are dropped (`Removed` fires after the loading completes). note that in that case, processing based on `Loaded` won't have been done anyway. i think we should get rid of `Unused` completely, it is not currently used anywhere (except here, previously) and i think using it is probably always a mistake. i also am not sure why we keep loading assets that have been dropped while loading, we should probably drop the loader task as well and remove immediately.~~ |
||
|---|---|---|
| .. | ||
| io | ||
| processor | ||
| server | ||
| assets.rs | ||
| direct_access_ext.rs | ||
| event.rs | ||
| folder.rs | ||
| handle.rs | ||
| id.rs | ||
| lib.rs | ||
| loader.rs | ||
| meta.rs | ||
| path.rs | ||
| reflect.rs | ||
| saver.rs | ||
| transformer.rs | ||