1. ## GetProperty(Application.Current.Host.Content, "ScaleFactor");

Hi,

with the line

GetProperty(Application.Current.Host.Content, "ScaleFactor");

I get 3 differnet values till now (100,150,160) depending on the screen resolution of my device. Does anyone know already what the value will be with the coming full HD devices (1980*1080)?

2. ## Re: GetProperty(Application.Current.Host.Content, "ScaleFactor");

We can only guess - none of that information has been made public but is expected to be when Nokia announces a new Windows Phone with a screen resolution of 1080p (with the GDR3 update), there's a Nokia event planned for Oct 22nd.

3. ## Re: GetProperty(Application.Current.Host.Content, "ScaleFactor");

It seems to be simple math to me: 480 is the base, 720=480*1.5, 768=480*1.6.
For 1080 it may happen to be 225 perhaps (1080=480*2.25). Remember this is just a calculation, rumors are not commented on this site.

4. ## Re: GetProperty(Application.Current.Host.Content, "ScaleFactor");

Originally Posted by theothernt
We can only guess - none of that information has been made public but is expected to be when Nokia announces a new Windows Phone with a screen resolution of 1080p (with the GDR3 update), there's a Nokia event planned for Oct 22nd.
Yeap... personally I would not expect the to have the confirmation before the SDK is out.

In any case I tried to do some math and came to this conclusion.

If 480 = 100
then 720 = 720 * 100 / 480 = 150
then 768 = 768 * 100 / 480 = 160
then 1080 = 1080 * 100 / 480 = 225

if you try to to the same with tha largest side you get:
If 800 = 100
then 1280 = 1280 * 100 / 800 = 160
then 1080 = 1080 * 100 / 800 = 247.5

My guess is that it will be 220 - 230. But this is just a guess.

Edit: Just saw wizard post. He got to the same number as I did - 225. take it with a grain of salt

5. ## Re: GetProperty(Application.Current.Host.Content, "ScaleFactor");

so I have to wait to get a confirmed value

6. ## Re: GetProperty(Application.Current.Host.Content, "ScaleFactor");

Originally Posted by MaHanno11
so I have to wait to get a confirmed value
We have now the confirmation here:

http://blogs.windows.com/windows_pho...evelopers.aspx

It will not be 225 but will remain 150 as for 720pix.

From the post:

Execution on a 1080p device

For the most part, you won’t need to know that your app is running on a 1080p phone - the existing APIs on a 1080p phone are quirked to behave as they would on a 720p phone and your app will work the same as it does today without any changes. For example:

- Querying for a 1080p phone’s resolution will report that the app is running on a 720p phone (ScaleFactor of 150, rather than 225)

- Apps that would letterbox on a 720p device will also letterbox on a 1080p phone

- Apps that have been opted out by the developer from a 720p phone in the Store also will be opted out from a 1080p phone

Because of this, most devs won’t need to do anything to target or test apps on a 1080p phone – the OS will take care of rendering for the resolution, the same as it does today. If you want to target 1080p phones with higher-DPI assets (e.g., images, splash screen, lock screen, live tiles, etc.), we suggest that you simply use high-DPI assets in your XAP package and let the OS properly downscale them as needed.

For those who want the app to behave differently on a 1080p phone, like rendering 1080p video streams or applying an alternative layout for larger screen devices, we have introduced a few new property values in the DeviceExtendedProperties class in the update. I’ll go into this in greater detail in a few weeks when we have a 1080p emulator for you to use.

7. ## Re: GetProperty(Application.Current.Host.Content, "ScaleFactor");

Thanks for info

#### Posting Permissions

• You may not post new threads
• You may not post replies
• You may not post attachments
• You may not edit your posts
•