Jump to content
  • Advertisement


  • Content count

  • Joined

  • Last visited

Community Reputation

127 Neutral

About Swatter555

  • Rank
  1. Swatter555

    DPI awareness and a full-screen

    I am stuck.   - I cannot compile the linked program because I have a poor mans version of Visual Studio.   - Even if I could compile the program and use it, DIrect2D automatically scales everything if I declare my application as DPI aware.   Bottom line, unless I figure out how to disable Direct2D automatic scaling, I cannot implement a custom scaling solution. Unless someone can tell me a way to disable virtualization without making my application DPI aware.
  2. Swatter555

    DPI awareness and a full-screen

    marcClintDion-   Thanks for the tutorial. It helps to go back and think about the basics. As I was thinking about supporting different resolutions, my first thought was just to express all graphical elements as a percentage of the viewing surface. Say a button would be 2% by 1.5%. I haven't really had much time to test it, but it seems like a good idea. Although, I would imagine the screen would not be a carbon copy across all resolutions, but then again that might be ok.   Then again, I really cannot escape the logic of what irreversible is saying. I guess that is the answer.   As I said though, Direct2D automatically scales, but I would assume that can be disabled. I wish someone would write a book on Direct2D, MSDN is only so useful.   Let me see about implementing a true scaling method like irrev is talking about. Ill test it across various settings and get back to you.
  3. Swatter555

    DPI awareness and a full-screen

    I will do my best to understand here, I am pretty tired so hopefully I make sense.   PunCrathod-   In Visual Studio Express 2012, there is a flag for DPI awareness that says it automatically makes changes to the manifest. At least that's what it says. Does that not really work?   I may be tired, but doesn't the formula: <horizontal DPI> * <width, in pixels> / <default horizontal DPI> result in a larger window at higher DPI?   I must not be understanding what is going on correctly, but when someone changes their DPI, they are wanting larger text and icons. I read one MSDN page that encouraged people to use their max monitor resolutions and just use higher DPI settings if they have trouble with small icons and print. I just don't see how that effectively increases monitor resolution. You have bigger text and other items in the same space.   Unless you are truly dealing with a display device that handles higher dpi, your just resizing your display elements. I am missing something.   irreversible- Thanks for the link. Once I understand what the heck Windows and Direct2D is doing, that something I can look into.
  4. I have been trying to Google combinations of those terms like crazy and I can find very little info. I am coding a full-screen application using the DIrect2D API, which automatically scales rendering to current DPI setting. That is all fine and dandy, but higher DPIs effectively decreases resolution. If I were creating a windowed app, I would create a larger window and everything would scale nicely. However, for full-screen, part of the screen is going to be clipped.   I have turned up very little info on my internet searches, so I am kinda stuck about what I should do. I could make the app use windowed mode, but that opens up a can of worms in itself. Direct2D uses dips for everything, so I don't think I can tell it not to scale things. What am I missing about DPI awareness and full-screen applications?        
  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!