Linking tokens overwrites destination elevation's linked token data.

[melek]

This issue doesn't matter when linking to the currently loaded elevation, but when linking a token to another elevation the current elevations tokens will be copied entirely to the destination elevation, totally wiping out the destination's elevation data.

To reproduce:

• Set up two key elevations, such a 0 - Ground and 100 - Sky.
• Create two tokens, such as Mage and Eagle from the default tokens.
• Switch to 0, click on the Mage token, and link it to elevation 0.
• Switch to 100, click on the Eagle token, and link it to elevation 100.
• Now, switch to view the 0 - Ground elevation and link the Mage token to 100 - Sky. This means the token will be visible at both elevations.
• Switch to the Sky elevation.
• See Error: The Sky elevation only has one token, the Eagle is not linked to either layer, and using the Map Explorer you can see it is far off-map in the area reserved for hidden elevation tokens.

Expected behavior:

• The Mage token should be added to the 100 - Sky key elevation so that both the Mage and Eagle are linked to it.

Discussion: Being able to link to other key elevations is important during a game, so you don't have to disrupt the players' view of the map to attach objects (such as downed foes) to a particular elevation to de-clutter the map.

[melek]

This has been solved in Lib:Elevation 1.0b2 with an update to the saveElevationTokens method.