HOME | DD

Resizing Icon — Description
96 frames. I'm really glad this didn't get corrupted along the way.

Some mythology:

Here we see an icon getting resized to its minimum size, 16x16.
To contain all its basic functions (read, write, add, remove, create, delete, open, close), it can't get any smaller than 16x16.
The only exception is if it gets damaged/corrupt.

What's not seen in this animation is how it can expand to its full size 32x32.
However in that state it becomes sluggish.
A smaller icon is faster, but will contain less data.

There are some issues to regard.
At the start of their creation, "young" icons, 16x16, have small dogtags in their upper right corner. I'm unsure if a "mature" icon like this should keep its dogtag size or if it should change while resizing.
One argument to keep it this way would be that this make it easier to separate young icons from resized mature ones.
A mature icon can not resize if it is filled with data.

Query: Does a mature icon's data compress during resizing?
Does emptying a mature icon's data make it young again?

Query: Does the transparency of an icon count to its size? Does an icon generate its own transparency inside a square area?
If so, a small icon would truly be 16x16, and not 32x32 with an excess of transparency.
The dogtag would then be a symbolic statement of the icon's ability to control its own design.