# Scaling issues on Windows

**URL:** <https://forum.juce.com/t/scaling-issues-on-windows/32138>\
**Category:** Windows\
**Created:** [March 6, 2019, 9:49pm UTC](https://forum.juce.com/t/scaling-issues-on-windows/32138 "2019-03-06T21:49:50Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![ed95](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/ed95/32/7635_2.png) [@ed95](https://forum.juce.com/u/ed95)\
**Post date:** [March 13, 2019, 9:11am UTC](https://forum.juce.com/t/scaling-issues-on-windows/32138/9 "2019-03-13T09:11:11Z")

</div>

No, I think you’ve misunderstood what I was saying. You linked to [this commit](https://forum.juce.com/t/issues-with-setglobalscalefactor-on-windows-standalone-in-latest-dev/29291/16) in your original post which would only have an effect on the OpenGL renderer. The `JUCE_WIN_PER_MONITOR_DPI_AWARE` flag changes the behaviour of both the software and the OpenGL renderer.

---

_[View the full topic](https://forum.juce.com/t/scaling-issues-on-windows/32138)._
