Multiple Texture Atlases in Skin constructor

Issue details

I’m suggesting that Scene2D have support for multiple Texture Atlases in Skin, here’s how I think it’ll work:

Skin.java Before:

/** Creates a skin containing the resources in the specified skin JSON file. If a file in the same directory with a ".atlas"
 * extension exists, it is loaded as a {@link TextureAtlas} and the texture regions added to the skin. The atlas is
 * automatically disposed when the skin is disposed. */
public Skin (FileHandle skinFile) {
    FileHandle atlasFile = skinFile.sibling(skinFile.nameWithoutExtension() + ".atlas");
    if (atlasFile.exists()) {
        atlas = new TextureAtlas(atlasFile);
        addRegions(atlas);
    }

    load(skinFile);
}

[...]

/** Creates a skin containing the resources in the specified skin JSON file and the texture regions from the specified atlas.
 * The atlas is automatically disposed when the skin is disposed. */
public Skin (FileHandle skinFile, TextureAtlas atlas) {
    this.atlas = atlas;
    addRegions(atlas);
    load(skinFile);
}   

After:

• Note I haven’t tested this, I’m on the edge that it works…

/** Creates a skin containing the resources in the specified skin JSON file. If a file in the same directory with a ".atlas"
 * extension exists, it is loaded as a {@link TextureAtlas} and the texture regions added to the skin. The atlas is
 * automatically disposed when the skin is disposed. */
public Skin (FileHandle skinFile) {
    for(FileHandle sibling : skinFile.parent().list())
            if(sibling.extension().toLowerCase().equals("atlas")) 
                addRegions(new TextureAtlas(sibling));
    load(skinFile);
}

[...]

/** Creates a skin containing the resources in the specified skin JSON file and the texture regions from the specified atlas.
 * The atlas is automatically disposed when the skin is disposed. */
public Skin (FileHandle skinFile, TextureAtlas ... atlases) {
    this.atlas = atlas;
    for(TextureAtlas atlas : atlases) addRegions(atlas);
    load(skinFile);
}   

[NathanSweet]

Create an empty skin with new Skin() and populate it with multiple atlases by calling addRegions(TextureAtlas) multiple times. The only difference is you will need to dispose the atlases yourself, whereas when using the constructor the skin owns the atlas and disposes it with the skin.

[cypherdare]

Maybe instead of cluttering Skin, add the ability to merge TextureAtlases. It could have a merge method that takes a parameter for how to handle name collisions (omit the regions vs. modify their names).

This potentially is more versatile. I didn’t understand the reason for needing multiple atlases at first, but I can think of one use case. If you have some parts of your skin that are resolution independent, while you have some that need multiple sizes, it might be handy to put them in separate atlases so you never have to load anything whose size is unneeded on the installed device. However, this could cause a lot of batch flushing.