PowerToys
PowerToys copied to clipboard
microsoft
Quick Accent diacritic overlay does not appear when triggered on a second monitor
Microsoft PowerToys version
0.62.0
Running as admin
- [X] Yes
Area(s) with issue?
Quick Accent
Steps to reproduce
In a text box present anywhere in a second monitor, trigger Quick Accent by holding a supported letter (e.g. "o") and activating Quick Accent with the appropriate activation key.
✔️ Expected Behavior
The diacritic selection overlay should appear at the top of the screen allowing one to choose the correct letter, as it does when triggered from a text box on the primary monitor.
❌ Actual Behavior
The overlay does not appear on either the secondary nor the primary monitor. Releasing the keys will give you the default diacritic (in the leftmost position of the overlay, if it could be seen). It does not seem to matter what program it's triggered from, the overlay will not appear.
Other Software
Note, in my setup the primary monitor is 3840x2160 but the secondary monitor is 1680x1050. In troubleshooting I also attached a very elderly 1024x768 monitor (lol) and it also presented the problem. Unfortunately I don't have access to a 1920x1080 or larger monitor for what is probably more realistic testing.
The 4K monitor is normally set to 200% scaling. I changed it to 100% for testing, it made no difference.
Monitors are driven by an nVidia GTX 1660, driver v516.94 (latest release as of time of writing). I upgraded the driver from v514.something (sorry, didn't write it down) while troubleshooting, same behavior on both.
I'm having issues too here. Got a Surface Pro with a built-in screen [2736 x 1824 @ 200%] and it shows the toolbar in the correct position - according to PT Settings. Then I also have a 1920 x 1080 (100%) external display and the positioning there is... very wrong. Looks like the scaling factor is faulty, making the toolbar off-screen for some settings. @dziban303 Can you test/verify different position settings?
Not confirmed with two identically sized monitors (1920*1080 with 100% scaling).
Not confirmed with two identically sized monitors (1920*1080 with 100% scaling).
@watchmakerful That, I could have predicted, since that is exactly what I'm not after :)
CAUSE: SCALE FACTOR IS WRONGFULLY CALCULATED
Red markings are the positions of the toolbar, in my case
Now at 150%
@dziban303 Can you test/verify different position settings?
I've tried all the position options. They work as expected on the primary monitor but do not appear at all on the secondary monitor. I thought one of them would work, but alas no. This probably has something to do with it:
Yeah, it looks silly, but it works for me in that when moving the mouse from one monitor to the other, it appears in roughly the right area, instead of like six inches higher or lower.
This issue is a bummer for me because the program I'd use Quick Accent with the most is always on the second monitor, so at the moment it's unusable with my current workflow. And it's uncomfortable to read the text when the primary monitor is scaled lower than 200%. Woe.
I've tried all the position options.
Did you try combinations of scaling too? Like, all to 100% or all to 200% or something?
I tried different combos yes. But restarting powertoys seemed to fix it with my normal scaling, thanks! Not sure why I didn't try that before.
This is back with 0.63. I don't see the GUI if I trigger Quick Accent on my second monitor. It works normally when I trigger from my primary monitor. Last time, I was able to get it to work by restarting PowerToys or restarting the Quick Accent module. This time neither option works. PowerToysReport_2022-10-07-16-15-14.zip
This PR https://github.com/microsoft/PowerToys/pull/21200 might fix this issue as well.
I'm not sure this PR will fix it. I take account DPI in PowerAccent, but in multi monitor with different DPI it is not so easy. I started to work on a fix on my side, and an improvement should be soon available (so I will be able to improve it in PowerToys too). Therefore it will not take account all situations, only the most common.
On my side I made some test today, and indeed it fixed things. I don't have any issue on my side anymore. Therefore I don't understand yet how it's can work. Calculate the screen size of a second monitor, with the dpi of the primary monitor is a non-sense to me. If someone have an explanation somewhere? (I have the feeling finally for the screen position WPF is based only on primary monitor informations, even if the window is in an another one).
Yep, on my side testing v0.64 the position seems to be good now. @jaimecbernardo maybe this issue was overlooked in the 0.64 Project?