I dont know, but should you be hard coding the dpi with applicationDPI="160"
wouldnt that mean you are always using the 160 image and scaling it up, hence the loss of quality.
dont know, just a guess
the application DPI is 160 in TabbedViewNavigatorApplication tag, but the framework should take the correct bitmap when my app run at 240 or 360 DPI and don't scaling up!
Should do the same thing that MultiDPIBitmapSource class does... :-(
just had a look at the link you pasted and they dont set the applicationDPI in the application tag
Setting the application dpi shouldn't affect the splash screen (you can verify by testing when you don't set the app dpi or by debugging the function). The dpi that gets passed in to the imageClass should always be the runtime dpi.
I see that in your MultiDPISplashScreen class extends CustomSplash instead of the SplashScreen. Maybe that could be the issues, where does CustomSplash come from?
The issue seems to be that in the SplashScreen class we don't undo the automatic dpi scale factor when the scaleMode="none" (the default). When this is combined with different images per dpi, this will cause the observed behavior. Setting scaleMode to any other value should fix the issue.
If you need to have the image centered and not scaled, then you may follow the work-around posted by Uggers at the end of the thread (bottom of the page) at http://www.adobe.com/devnet/flex/articles/mobile-skinning-part2.html#articlecontentAdobe_n umberedheader_5
thanks for your reply!
Great!!! The work-around posted by Uggers does works!!!and I had not read the last post!
Many many thanks!!