LibGDX the correct way of using AssetManager

Question

In the Managing your assets is said that the following coded will cause issues public static AssetManager assets = new AssetManager(); But i do not understand the difference between above code and the next code:

public class AssetSingleton {    
    private static final AssetSingleton instance = new AssetSingleton();

    private final AssetManager assets = new Assets();

    public AssetManager getAssets(){
        return assets;
    }
}

...........................................

AssetManager manager = AssetSingleton.instance.getAssets();

So why the first code is unsafe when pausing/resuming the android app? Where and in what way i have to store the AssetManager instance? There is no example in the LibGDX docs. In book "Learning LibGDX Game Development 2nd Edition" there is used singleton with the instance of assetmanager and on resume/pause this singleton loads/unloads resources.

Also is said in Managing your assets:

If you don't set the AssetManager as shown in the last snippet, the usual managed texture mechanism will kick in, so you don't have to worry about anything.

Do i understand correctly: if ihave no singleton and i do not use the static instance of AssetManager - the assets will be loaded and unloaded by LibGDX automatically. If so - how? Whats the difference?

Abhishek Aryan Abhishek Aryan · Accepted Answer · 2017-07-15T11:09:03

Having static references to assets is especially bad, because the life cycle of the statics might not be the same as the life cycle the context the resources are created in. Check this answer for detail.
If you want to show Loading Screen while Resuming your game, You've to use
```
Texture.setAssetManager(manager);
```
If you don't set the AssetManager as shown in the above statement, the usual managed texture mechanism will kick in, so you don't have to worry about anything.

LibGDX the correct way of using AssetManager

1 Answers