starred/PlayCover

Fork 0

mirror of https://github.com/PlayCover/PlayCover.git synced 2026-04-26 08:15:56 +03:00

[GH-ISSUE #1891] [Bug]: Resizable apps do not have correct click placement with playchain #1239

New issue

Open

opened 2026-03-03 19:05:01 +03:00 by kerem · 5 comments

kerem commented

2026-03-03 19:05:01 +03:00

Owner

Originally created by @Melonchanism on GitHub (Jun 11, 2025).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1891

Describe the bug

When an app is resizable and is enabled to do so via fix window display issues, clicking actually assumes that the app is still the same size, and the clicks are remapped to a scaled version of the original app size

Steps to reproduce

Install a resizable app (eg google classroom).
Enable fix window display issues to let the app resize to the window size
Turn on click debugging (to see where the simulated click happens)
Click somewhere closer to the bottom right and see the offset

Expected behaviour

The clicks should go to exactly where the click happened (like without playchain)

Crash log

What version of PlayCover are you using?

3.1.0

What version of macOS are you using?

Sonoma (macOS 14)

Issue Language

Yes my issue is written in English

Originally created by @Melonchanism on GitHub (Jun 11, 2025). Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1891 ### Describe the bug When an app is resizable and is enabled to do so via fix window display issues, clicking actually assumes that the app is still the same size, and the clicks are remapped to a scaled version of the original app size ### Steps to reproduce Install a resizable app (eg google classroom). Enable fix window display issues to let the app resize to the window size Turn on click debugging (to see where the simulated click happens) Click somewhere closer to the bottom right and see the offset ### Expected behaviour The clicks should go to exactly where the click happened (like without playchain) ### Crash log ```shell ``` ### What version of PlayCover are you using? 3.1.0 ### What version of macOS are you using? Sonoma (macOS 14) ### Issue Language - [x] Yes my issue is written in English

kerem added the

bug

label

2026-03-03 19:05:01 +03:00

kerem commented

2026-03-03 19:05:02 +03:00

Author

Owner

@TheMoonThatRises commented on GitHub (Jun 22, 2025):

@XuYicong can you take a look at this?

@TheMoonThatRises commented on GitHub (Jun 22, 2025): @XuYicong can you take a look at this?

kerem commented

2026-03-03 19:05:02 +03:00

Author

Owner

@Melonchanism commented on GitHub (Jun 23, 2025):

For reference if the window is the exact same size as the content without fix display issues, the clicks will be scaled one to one and will be correct

@Melonchanism commented on GitHub (Jun 23, 2025): For reference if the window is the exact same size as the content without fix display issues, the clicks will be scaled one to one and will be correct

kerem commented

2026-03-03 19:05:02 +03:00

Author

Owner

@Melonchanism commented on GitHub (Jul 21, 2025):

https://github.com/user-attachments/assets/c23e5aac-c8c8-4ee6-bb65-2786d6824813

Here's a sample (sorry that you can't see the text

@Melonchanism commented on GitHub (Jul 21, 2025): https://github.com/user-attachments/assets/c23e5aac-c8c8-4ee6-bb65-2786d6824813 Here's a sample (sorry that you can't see the text

kerem commented

2026-03-03 19:05:02 +03:00

Author

Owner

@Gustqve commented on GitHub (Sep 5, 2025):

I indeed have the same problem with SoundCloud, I thought the "fix window display issues" option would fix it but it moves the clickable area as well...

@Gustqve commented on GitHub (Sep 5, 2025): I indeed have the same problem with SoundCloud, I thought the "fix window display issues" option would fix it but it moves the clickable area as well...

kerem commented

2026-03-03 19:05:02 +03:00

Author

Owner

@Melonchanism commented on GitHub (Dec 17, 2025):

@Gustqve I found a fix with a compromise: If you disable keymapping it works fine

@Melonchanism commented on GitHub (Dec 17, 2025): @Gustqve I found a fix with a compromise: If you disable keymapping it works fine