ID:260795
 
Status: Open

Issue hasn't been assigned a status value.
...other stuff being stuff that has a background image (like output controls).

It'd basically work like the DM icon editor does now: it allows you to add/remove "frames". You can assign images to these frames.

By default, a(n) (background) image consists of only 1 frame. But you can set it to multiple frames and pick different images.

In addition you can also set the delay for each frame, just like you can do with the icon editor. What the client would have to do is provide the animation in pretty much the same way that it happens on the map.

Alternatively it could be made possible to select a .DMI as an image and specify the icon_state to use. If the state has multiple frames, it'd loop through these frames. Since DMI files can already have greater than 32x32 sizes, and because they already contain the information for delays and frames, it should be relatively easy to use.
Android Data wrote:
It'd basically work like the DM icon editor does now: it allows you to add/remove "frames". You can assign images to these frames.

You should indeed stick with the latter idea; the above one would just needlessly complicate things, and would also need to make changes to winget() (or alternatively, past code that calls it) and as such.

How you designate a background image and all shouldn't change; it should only be an internal change, that background images now support animated DMI (and why not GIF) files, by whatever method for it they come up with.

Like you said this should really be widely implemented into all controls, i.e. globally or something to that extent. So all controls support animated image files as their image, background image, whatever image, etc (e.g. animated buttons). Maybe even in browsers controls, but that would require browse_rsc() to automatically convert animated DMIs to animated GIFs. >_>
2009 so it really should've been reviewed by now
Bump