diff options
| author | hbono@google.com <hbono@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-09-14 10:13:14 +0000 |
|---|---|---|
| committer | hbono@google.com <hbono@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-09-14 10:13:14 +0000 |
| commit | 8e0b4a087506b2a9a3c4541489d442fd36eaf976 (patch) | |
| tree | 90cab20fe99f866313c9943dbfa82f057836ca8d /app/win_util.h | |
| parent | a363a84f1e52b958d0aa04d2d5554b5f949908cc (diff) | |
| download | chromium_src-8e0b4a087506b2a9a3c4541489d442fd36eaf976.zip chromium_src-8e0b4a087506b2a9a3c4541489d442fd36eaf976.tar.gz chromium_src-8e0b4a087506b2a9a3c4541489d442fd36eaf976.tar.bz2 | |
Revert 52446 - Supports High DPI mode.
This change caused too many layout problems; such as Issue 50100 and 51562. I would like to revert this change now and send another change when I fix them.
When launching an application on the text size larger than 120 DPI, Windows runs the application on the DPI-virtualization mode to hide the text size from it. Unfortunately, this virtualization mode causes some problems when using a custom frame, such as we cannot click system buttons. To fix this issue, this change disables the DPI-virtualization mode on Vista or later.
BUG=1715,36939
TEST=Run chrome.exe on the screen resolution higher than 120 DPI.
Review URL: http://codereview.chromium.org/2867031
TBR=hbono@chromium.org
Review URL: http://codereview.chromium.org/3435002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@59353 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'app/win_util.h')
| -rw-r--r-- | app/win_util.h | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/app/win_util.h b/app/win_util.h index 30bfd83..2aecea5 100644 --- a/app/win_util.h +++ b/app/win_util.h @@ -216,13 +216,6 @@ extern const int kAutoHideTaskbarThicknessPx; // do not group together on the Win7 task bar. void SetAppIdForWindow(const std::wstring& app_id, HWND hwnd); -// Calls SetProcessDPIAware() to declare this application is DPI-aware and to -// disable the DPI virtualization of Windows. Unfortunately, calling this -// function after creating a window confuses some APIs, i.e. some APIs still -// have the DPI virtualization enabled after calling SetProcessDPIAware(). -// Therefore, we need to call this function before creating the first window. -void CallSetProcessDPIAware(); - } // namespace win_util #endif // APP_WIN_UTIL_H_ |