You shouldn't need to change any css. A 12 - 14pt font face in 160dpi is about like the typical body text you'll see in most mobile apps. But if your app is running on a 480 dpi display that 14pt font (still the same property setting or css) will appear roughly the same size as the typical body text you'll see in most mobile apps.
You never need to change font sizes or use any css directives to change font sizes, ever. It's unnecessary because the designers of Flex/Flash were smart about making it easy for your app to look good on all devices without changing any settings but the runtime DPI. Oh, and if you don't extend the default RuntimeDPIProvider with your own settings, it will still map higher DPIs to scaled fonts and layouts. The only real need for your own RuntimDPIProvider is where the defaults aren't quite as good as you want. I always develop AIR apps with applicationDPI="160" which makes my optimal font sizes feel more like fonts you might set in a Word document, so instead of a high application DPI where your font has to be like 30pt for regular text, you can work with more intuitive sizes, e.g., 12-14pt for body text, 16 for h3, 18 for h2 and 20 for h1, or something like that. Anyway, don't over think this. All the hard work has been done for you. On Mar 19, 2019, at 11:54 AM, agm65 <agm65maver...@gmx.de> wrote: Hi Erik, thanks alot for your answer. For my better understanding: The runtimeDPI value is the value of my device and it sets my applicationDPI value to one of those 6 values (120-640). And this applicationDPI value is used in the css to switch my font sizes etc? So with defining new ranges i can finetune my settings. got it? -- Sent from: http://apache-flex-users.2333346.n4.nabble.com/
