ID:1935890
 
Applies to:
Status: Open

Issue hasn't been assigned a status value.
I was considering making a bug report, but I am not quite sure of the actual intent of "\icon". So, suggestion for now, bug report if someone can confirm the actual full purpose of it.


So, as far as I am aware, the only way to show an image on the statpanel is via either using a manually-defined
"<img>"
tag, or \icon. However, this raises a problem, as \icon currently only shows the base icon of an object, with none of it's overlays.

My suggestion is thus; A new version of \icon, which does include the overlays of the referenced object. No idea how feasible it is.
You can build the icon yourself using the /icon datum and Blend(). I do see a point in allowing the macro to be expanded so it can handle taking a known object's appearance, though.
Being able to assign an icon a known appearance would be a godsend in replacing certain functions in our code (linked below) that artificially remake the appearance on the icon object.

For OP's purposes our implementation would probably be sufficient, if a little costly when called often. It is general enough that it could probably be operational with almost any code with just a little bit of tweaking.

http://puu.sh/kbD9m/d794e66553.txt
In response to Clusterfack
Looks like a heavily modified version of Get Flat Icon. Might be easier for Tigercat2000 to include the library, since otherwise they'll have to tear out the extra directional_turfs foo. As a bonus, it includes a demo and documentation :)

+1 to having this built-in, though. The soft-coded versions are far from full coverage of BYOND's features.
That is precisely the case, nice catch
I do see a point in allowing the macro to be expanded so it can handle taking a known object's appearance, though.

So much this.
A big plus one to this, especially if it could be made faster than a soft coded approach!
Bump, this would be awesome to have
The ability to turn appearances into /icons would also solve this.
++