It's hard to export the appearance of something, it requires you to do all the operations on the overlays, underlays, etc... and that's probably gonna get even harder with 510 due to KEEP_TOGETHER.
It'd be incredibly nice if there was a proc like appearance.toIcon() that "exported" the appearance to a /icon datum for use in other procs (a big one that comes to mind is browse_rsc()).
Another way to do it would be icon(appearance) or something like that, which wouldn't require a new proc to be added.
ID:2039888
Feb 19 2016, 10:39 am
|
|||||||
Resolved
| |||||||
Feb 19 2016, 11:41 am
|
|
Agreed, we actually brought this up to Lummox when he was first implementing the appearance variable, he said it was doable but not priority.
|
This feature would be very helpful for icon handling and consistency on in-game images, for example.
|
the suggested syntax was just to make the icon() proc support taking in an appearance.
|
Another potential idea somebody gave me for the syntax could be something like an appearance var on icons, then doing icon.appearance = otherappearance would have the same effect.
Not my idea though. |
bumping this after growing a few grey hairs trying to optimize our getFlatIcon() proc while thinking man, if only there was a byond way to do this.
|
I +1 this every time someone bumps it, bump bump, been bumping it since before the feature existed in the language.
|
+1, mostly for the same reasons MSO gave; getFlatIcon, at least as used on Bay, is ludicrously slow.
|
Icon flattening is slow, no matter how you do it, I've tried soooo many different methods.
|
Perhaps a lot of work to make, but it would be an extremely useful feature for those using the language.
|
After encountering yet another bug/oddity with our hacky getflaticon(), I have come to only one conclusion, we NEEDS this.
|
In response to MrStonedOne
|
|
Honestly surprised it took you this long to come to that conclusion to be honest.
|