search

ngld / OverlayPlugin

Yet another OverlayPlugin fork.
Other
231 stars 39 forks source link

Overlays taking on Windows 10 display scaling #13

Open royblazer opened 4 years ago

royblazer commented 4 years ago

I just upgraded to the newest pre-release (0.8.1 from old 0.3.4.0). Just noting this as this was the only major change since this issue popped up.

Upon starting up ACT, the overlays I have take on the higher display scaling of my two monitors (basically 125% size rather than 100%). Even if ACT starts up on the non-scaled monitor, the overlays take the scaled settings of the other. If I readjust the overlays, they go back to non-scaled size. When re-opening ACT, positions keep, but the scaling reverts back to that of the secondary monitor.

Is this something fixable?

ngld commented 4 years ago

I'm not sure since I haven't had to deal with high DPI issues, yet. I think ACT itself isn't DPI aware. Have you tried experimenting with the DPI related compatibility settings?

When OverlayPlugin starts up, it sets the overlay size to the same value it was at when ACT was last closed so it doesn't make much sense (to me) that the overlays would change their size between restarts.

royblazer commented 4 years ago

Unfortunately yup, I've tried fiddling around with the DPI compatibility settings. I'll try messing around a bit more, but overall not an end of the world problem since it still works in general. :)

royblazer commented 4 years ago

Just an update, I managed to get the high DPI scaling override to work by setting it to Application (not sure why it didn't work when I tried it before). I'm still not entirely sure why this started to happen, but hopefully this can help anyone else who winds up encountering this particular issue.

Thanks!

ngld commented 4 years ago

I don't think I can really fix this. ACT itself isn't DPI aware and if I started to mess with that, it's very likely I'd break something else. The only solution I can see right now would be launching a second process that is DPI aware and renders the overlay instead of ACT itself. That's going to be a lot of work (since all of the log events, etc.) would have to be passed between the two processes. I probably won't work on something like this any time soon.

toastyc12 commented 4 years ago

I'm also having DPI issues with this plugin that I wasn't having with Hibiyasleep. I have my ACT configured to start up in 150% scaling, but as soon as overlayplugin loads, it reverts back to 100% again. I'll also try fiddling with scaling options again, I just wanted to drop by here to see if anyone else had the same problem.