I suggest to move to my Accelerated Surface library for at least two reasons: there's no strange result with KitKat and you benefit from the hardware acceleration.
If that works well with the change made by Erel, no you have nothing to do. My advice was a general advice in case you'd have strange issues with KitKat or you just want something more powerful. The canvas is, to my eyes, a deprecated class. I replaced it almost everywhere in my own code by the AS library to do the same thing. AS is faster, draws with anti-aliasing enabled, offers a lot more possibilities and its ease of use is very similar. But these two libraries are not exactly used in the same way (AS uses a Draw event), so you will have to rewrite some parts of your code.
Google discourages explicitely the use of GIFs (and IMHO this format is completely outdated) so you should convert your GIF to PNG. You have no guarantee that it will be supported in the future.
I use it cause they take up less space than the same image in PNG, and take less work (I run my PNGs through tinyPNG.com)
They shouldn't be screwing devs over on a whim like this...
I use it cause they take up less space than the same image in PNG, and take less work (I run my PNGs through tinyPNG.com)
They shouldn't be screwing devs over on a whim like this...
Supporting a format limited to 256 colors on a device able to display millions of colors is a strange choice from my point of view. I think that they added the support of GIF at the beginning because of the many web sites still using it, but even on Internet, this format is disappearing and some day this format will be definitely a thing of the past. I don't think that the difference with a PNG is huge after going through tinyPNG.