[Bug]: Token footprint is kept when changing to native size

[kwvanderlinde]

Describe the Bug

If a Medium token (1x1 cell) is changed to Native size, the footprint stays as one cell. If a Gargantuan token (4x4 cells) is changed to Native size, its footprint stays as 4x4 cells despite the user seeing no reference to a Gargantuan size.

To Reproduce

1. Drag two tokens onto a map with square grid
2. Change one token to size Medium and the other to size Gargantuan
3. Change both tokens to size Native.
4. Drag each token. Notice the originally-medium token still occupies one cell, while the originally-Gargantuan token occupies 16 cells

Expected Behaviour

The token footprint should be based on its actual size. If the token visibly covers 9 cells, that should be its footprint. Alternatively, natively-sized tokens could simply occupy one cell at its center.

Screenshots

This shows the two apparently-identical tokens with their differing footprints:

MapTool Info

1.14.3

Desktop

Linux Mint 21.3

Additional Context

No response

[bubblobill]

• Native size footprints should probably be the size of the drawn image instead of one cell.
• I can actually see benefits in this if it was something you could do deliberately. e.g. A token has an effect that covers a certain footprint. You could then use macros to apply the effect on other tokens within the footprint.
• We really need a footprint editor dialogue

[bubblobill]

No. What you see is not necessarily related to the occupied space.
WRT retention of footprint. That should just need isSnapToScale being set to false when it is changed to free-size
Between footprints changing, where do we need to update the occupied cells cache?