Thanks Gents - looks like a perfect fit for my needs
On 19/08/2013 06:43, Alex Harui wrote:
Potentially helpful article.
http://renaun.com/blog/2011/10/customizing-flex-applicationdpi-for-a-multip
le-screen-size-application/
On 8/18/13 7:58 PM, "Justin Mclean" wrote:
Hi,
b) Yes. This is h
Potentially helpful article.
http://renaun.com/blog/2011/10/customizing-flex-applicationdpi-for-a-multip
le-screen-size-application/
On 8/18/13 7:58 PM, "Justin Mclean" wrote:
>Hi,
>
>> b) Yes. This is how it's done...
>
>Not tried but I believe you can extend RuntimeDPIProvider class, and
>ove
Hi,
> b) Yes. This is how it's done...
Not tried but I believe you can extend RuntimeDPIProvider class, and override
the classifyDPI method to only return the buckets you want and then set the
application's runtimeDPIProvider probopety to be this new class.
Thanks,
Justin
Respectfully, no-one has attempted to answer my question yet:
I'm wondering if there is any way to switch off the new 120/480(?)/640
dpi features in 4.10 (other than monkey patching)?
I'll like the answer to be one of these:
a) No.
b) Yes. This is how it's done...
On 18/08/2013 19:06, OmP
On Sun, Aug 18, 2013 at 10:50 AM, Lee Burrows
wrote:
> Sorry if i was unclear, but i do care about high dpi devices - its just
> that i want them to continue to use 320dpi assets.
>
>
You can probably just point the source value for the higher dpis to your
320 dpi assets in that case.
Ex.:
Sorry if i was unclear, but i do care about high dpi devices - its just
that i want them to continue to use 320dpi assets.
On 18/08/2013 18:42, OmPrakash Muppirala wrote:
But that will happen only on devices that you don't care about - as you
mentioned. If no one is going to use your app in th
But that will happen only on devices that you don't care about - as you
mentioned. If no one is going to use your app in those unsupported dpis,
you dont need to worry about it.
Om
On Sun, Aug 18, 2013 at 10:39 AM, Lee Burrows
wrote:
> Yes, but i dont want the bitmaps to scale - they'll look p
But if a device is detected to be 640dpi, wont skins (eg button label)
use a font size appropriate for 640?
On 18/08/2013 18:17, OmPrakash Muppirala wrote:
The dpi settings are just buckets. Any other dpis will be approximated
(i.e. scaling in code) I think you should be able to just ignore
Yes, but i dont want the bitmaps to scale - they'll look poor if scale
isnt a power of 2 (eg: 320 scaled to 480).
On 18/08/2013 18:24, Justin Mclean wrote:
Hi,
An app i am working on uses a lot of MultiDPIBitmapSource instances for
(mainly) button icons, and i dont want to have to create new
Hi,
> An app i am working on uses a lot of MultiDPIBitmapSource instances for
> (mainly) button icons, and i dont want to have to create new .pngs at
> 120/480(?)/640 scale - i'd rather stick to using 160/240/320 skins/assets to
> save myself a lot of work.
You don't need to create the extra bi
The dpi settings are just buckets. Any other dpis will be approximated
(i.e. scaling in code) I think you should be able to just ignore the new
dpi features without affecting existing apps.
Thanks,
Om
On Sun, Aug 18, 2013 at 10:13 AM, Lee Burrows
wrote:
> Hi
>
> I'm wondering if there is any
Hi
I'm wondering if there is any way to switch off the new 120/480(?)/640
dpi features in 4.10 (other than monkey patching)?
An app i am working on uses a lot of MultiDPIBitmapSource instances for
(mainly) button icons, and i dont want to have to create new .pngs at
120/480(?)/640 scale - i'
12 matches
Mail list logo