We upgraded our internal version of SDL, which we use for native windowing, rendering and events. They have upgraded their minimum on the NDK-side to API 14 (Android 4.0), this was done a version or two ago, but we had some runtime errors with old devices because the minimum SDK API level wasn’t increased to match.
We’re supporting 99.8% of Android devices in the Play Store currently
Hmm. In fact I am doing an education app ( been a few years already …) I was planning to “recycle” old tablets and put my app on it to give them to people who need it. But maybe not so many old androids are left …
Saying this I forgot my old gingerbread phone somewhere, so it’s been a while I haven’t tested on it.
There’s a new app.meta object, which can be used for storing application meta-data. The default template uses these values:
(…though perhaps it should use “package” instead of “packageName”?)
EDIT: Looks like we’re missing “version”, but it could be added
EDIT2: If you use lime.embed, it appears that { rootPath: "path/to/asset/root" } should be available on window.config.rootPath, but it’s not strictly typed
Currently, we follow the format encoded in the SWF. If you set something to “lossless” in the Flash library, then it should be PNG in the SWF, otherwise it’s JPEG, or JPEG + ALPHA, which we encode as a JPEG and a PNG alpha file. It would be possible to do more, but currently we let the SWF file dictate what format to use
I added it in the develop branch of Lime, but for OpenFL, I added it to a working branch I have while I’m doing some breaking changes, until it stabilizes.
Could you double-check if you’re running the latest versions? It may include a fix that should help. You can also try -Dopenfl-share-context to see if that makes a difference
I just did a haxelib update and downloaded latest and greatest. I also tried try -Dopenfl-share-context as well and still same effect. This happens when I update the texture on the folder.
Hmm, strange. Native or HTML5? If HTML5, are there any errors in the console? What kind of texture is it (Texture, RectangleTexture, PNG, JPEG, ATF, etc)? Does adding -Dopenfl-disable-context-cache make a difference?
It’s the HTML5 export and using an textured JPEG that is being applied on roll over and out. I also added -Dopenfl-disable-context-cache and it’s having the same effect.