You can use the same methods as above however instead of placing the drawable resource in drawable place a version in each of the resolution specific directories: Next lets create the actual resource we will use for the splash in the ANE. You should find your AIR SDK packages normally and start with the expected black screen before loading your SWF. This is the resource that will be used if we don't package an ANE containing the override resource. Then lets create a fallback resource a simple 1x1 pixel black png called splash_background.png and place it in the AIR SDK at AIRSDK/lib/android/lib/resources/app_entry/res/drawable/splash_background.png. Lets start by again adjusting the AIR SDK by specifying a splash_background resource in the styles.xml resource located at AIRSDK/lib/android/lib/resources/app_entry/res/values/styles.xml: By providing a non resolution specific drawable resource in the AIR SDK and then overriding it with resolution specific versions. Normally this would result in a resource conflict however we can use a small trick here. This is done by setting up a default splash screen drawable resource in your AIR SDK and then overriding this resource with resources packaged in the ANE. This has the advantage of being able to modify the SDK once and then use a custom ANE to specify the splash screen for each of your applications, rather than have to modify the AIR SDK before each build. It is possible to to package your splash screen in a Custom Resources ANE. When using this method we advise that you add all the different dpi versions of your image to correctly support different screen sizes: Read more here: Resources in ANEs
0 kommentar(er)
