Note that there are some explanatory texts on larger screens.

plurals
  1. POScaling for Android devices with starling causing some layout issues
    primarykey
    data
    text
    <p>I'm using multi resolution technique number three as written in this <a href="http://wiki.starling-framework.org/manual/multi-resolution_development" rel="nofollow">article</a></p> <p>and to determine the scale factor and stage size, I'm using this piece of code originally written by Jeff :</p> <pre><code> if (Capabilities.screenDPI &gt;= 200) { if (Capabilities.screenDPI &gt;= 280) { AssetFactory.contentScaleFactor = 2; } else { AssetFactory.contentScaleFactor = 1.5; } } else { AssetFactory.contentScaleFactor = 1; } var mViewPort:Rectangle = new Rectangle(0, 0, stage.fullScreenWidth, stage.fullScreenHeight); mStarling = new Starling(Startup, stage,mViewPort); mStarling.stage.stageWidth = stage.fullScreenWidth / AssetFactory.contentScaleFactor; mStarling.stage.stageHeight = stage.fullScreenHeight / AssetFactory.contentScaleFactor; </code></pre> <p>Then I use this scale factor to determine which sized assets I need to pick.</p> <p>So now, I have a background which I strech to stage width and size. This technique works great when I'm testing with most devices but then we have devices like the Barnes and Noble Nook Color. </p> <p>The device has a resolution of 600x1024 with 170 dpi. This means that it's going to pick the smallest assets (320x480) and strech it to 600x1024. Which ofcourse is pixalated. Any ideas on how to get over this issue? </p> <p>I'm also attaching a test application which shows the issue in detail <a href="https://dl.dropbox.com/u/2192209/scaling%20test.zip" rel="nofollow">https://dl.dropbox.com/u/2192209/scaling%20test.zip</a></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload