-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Candidate window may be misplaced when Per-Monitor DPI setting is enabled in Windows #832
Comments
hiroyuki-komatsu
added a commit
that referenced
this issue
Oct 26, 2023
Typing quality * Added 鵼(ぬえ) and 喃(のう) to the word dictionary. Linux * Fixed the crash issue of the candidate window UI (#820) Windows * Enabled the candidate window to respect the vertical writing mode (#362) * Updated InputScope mapping to be compatible with MS-IME as of Windows 11 22H2 (#818, #826) * Addressed the issue of no response on MS-Word (#819) * Enabled the candidate window to consider per-monitor DPI settings (#832) Build * Enabled C++20 (#783) * Switched to Qt 6.6.0 for Windows and macOS (#833) * Reduced Qt6 binary size (#822) * macOS: Fixed the non executable error of GUI tools with GYP * Windows: Stopped specifying /BASE option (#834) * Windows: Enabled Hardware Enforced Stack Protection (#835) * Windows: Set default dependent load flags to Mozc executables for Windows (#836) * Windows: Removed the dependency on CoCreateInpustance from mozc_tip dlls (#837) PiperOrigin-RevId: 576830216
coooooooozy
pushed a commit
to coooooooozy/mozc
that referenced
this issue
Nov 26, 2023
This is a minimum change to place candidate windows around the cursor location even under Per-Monitor DPI mode in Windows. Note that there are still known issues that 'mozc_render' continues using the initial DPI. Watch google#831 for such remaining issues. Closes google#832. PiperOrigin-RevId: 575633393
coooooooozy
pushed a commit
to coooooooozy/mozc
that referenced
this issue
Nov 26, 2023
Typing quality * Added 鵼(ぬえ) and 喃(のう) to the word dictionary. Linux * Fixed the crash issue of the candidate window UI (google#820) Windows * Enabled the candidate window to respect the vertical writing mode (google#362) * Updated InputScope mapping to be compatible with MS-IME as of Windows 11 22H2 (google#818, google#826) * Addressed the issue of no response on MS-Word (google#819) * Enabled the candidate window to consider per-monitor DPI settings (google#832) Build * Enabled C++20 (google#783) * Switched to Qt 6.6.0 for Windows and macOS (google#833) * Reduced Qt6 binary size (google#822) * macOS: Fixed the non executable error of GUI tools with GYP * Windows: Stopped specifying /BASE option (google#834) * Windows: Enabled Hardware Enforced Stack Protection (google#835) * Windows: Set default dependent load flags to Mozc executables for Windows (google#836) * Windows: Removed the dependency on CoCreateInpustance from mozc_tip dlls (google#837) PiperOrigin-RevId: 576830216
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When Mozc is used under Per-Monitor DPI environment where each display has different effective DPI, Mozc's candidate window may not be shown at the expected location.
This is a sub task of the following effort.
Steps to reproduce
Expected behavior
Actual behavior
Screenshots
Version or commit-id
af20906
Environment
The text was updated successfully, but these errors were encountered: