locked
Update to Win 8.1/VS2013 Changed Resolution of App Window.Current.Bounds

    Question

  • Before I installed 8.1/VS2013 my app worked fine in my 1920x1080 resolution.

    It's a very specific project and will always run at 1920x1080, so I built it as such.

    Now that I've upgraded, everything was suddenly cropped.  It appears that from my Window.Current.Bounds that the resolution of the app window is now only 1366x768 even though my desktop is set to 1920x1080.  My display scaling is at 100% as well.

    What happened here? How can I tell 8.1 or VS2013 to run this app at native resolution again so that it appears properly?

    Thanks


    Michael Hawker

    Wednesday, October 22, 2014 10:43 PM

Answers

  • Hi Michael,

    I think this documentation is what you need: Supporting multiple screen sizes, check out the Dos and don'ts section for more information.

    You may want to design your app to fit all screen solution by dynamic layout. If you would like to programmatically design the layout during runtime, you could either use Window.Current.Bounds to get the current screen size.

    --James


    <THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
    Thanks
    MSDN Community Support

    Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

    Thursday, October 23, 2014 1:31 AM
    Moderator

All replies

  • Hi Michael,

    I think this documentation is what you need: Supporting multiple screen sizes, check out the Dos and don'ts section for more information.

    You may want to design your app to fit all screen solution by dynamic layout. If you would like to programmatically design the layout during runtime, you could either use Window.Current.Bounds to get the current screen size.

    --James


    <THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
    Thanks
    MSDN Community Support

    Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

    Thursday, October 23, 2014 1:31 AM
    Moderator
  • Thanks James,

    That is certainly a useful page.  Wrapping a viewbox around my content certainly fixes most of my immediate concerns.

    Ideally of course, you want to develop apps for varying sizes; the problem was this is a 'quick' one-off thing that was designed to run at a native 1920x1080 resolution.  Suddenly just upgrading the dev environment (I was still targeting win 8) and having my app behave entirely differently was disconcerting.

    That said, I understand the move to target a specific resolution and relative sizing and let the OS do more of the scaling work, but how do I turn this off and force it to give me my native resolution to work with again?

    Thanks,

    Michael

    Thursday, October 23, 2014 4:17 AM
  • I know there is another "quick" but not that good solution, set a Height and Width for the Page, or you could change to pre-set display option from device panel.

    I understand the move to target a specific resolution and relative sizing and let the OS do more of the scaling work, but how do I turn this off and force it to give me my native resolution to work with again?

    -> Besides the screen resolution, dpi is another thing you have to pay more attention. 148 dpi and 100 dpi shows different size of control and definitely you got different layout.

    Anyway, use internal channel to ask for more specific help if you are working for Microsoft. :)

    --James


    <THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
    Thanks
    MSDN Community Support

    Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

    Thursday, October 23, 2014 8:21 AM
    Moderator