-
Notifications
You must be signed in to change notification settings - Fork 539
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
MacOS: touch input incorrectly mapped #42
Comments
Are you using external firmware file |
Tried with external firmware and without. |
Upon further inspection, it seems that the touch input is mapped to both screens as if the touch screen is expanded to take the room of both screens. Just the left half it seems. |
@ArchKevin22, your analysis doesn't make any sense. Try playing a game like The Legend of Zelda: Spirit Tracks, which uses the touch screen to move Link around, and see if the problem persists. That game uses little sparkly stars to track the touch location in real time, so that should reveal the problem without any ambiguity. |
Here is a video of me attempting to start a new game in Zelda. |
@ArchKevin22, it seems like there may be a legitimate problem here. Please choose Help > Submit a Bug Report and follow the onscreen instructions. When you get to the end, copy-paste the information here, thanks! |
Should I post here or source forge? Which is more preferred? |
I'll start with here. App Version: 0.9.12 git#5e06fbc x64-JIT SSSE3 (LLVM-Clang v8.0.0)
|
No need to post it on SourceForge. Just posting it here is fine. |
Is there a way I can contribute? (as in help with the code) If I had some knowledge about how the touchscreen mapping works (and where the code in the touchscreen mapping is located in the project), I can attempt to mess around with stuff. |
You're using one of the new Touch Bar 2016 MacBook Pros, which has a Retina display, correct? Unfortunately, I haven't done a lot of testing on Retina displays, and I'm pretty sure that this issue has everything to do with that. I did a bunch of changes to that part of the code, and I may have broken something with Retina displays. The best way to contribute for now is to test previous builds and find out where the regression started. Here's some good places to start: 2016/12/30 - git#cf8f021 |
Broken on git#25c0232, the other two builds work fine. |
Yup, it's an issue with Retina displays. Most likely, I broke touch mapping on Retina displays in commit 858d14b, where I changed display views to use a CAOpenGLLayer instead of an NSOpenGLContext. This is definitely a fixable bug. |
Nice. |
When using the mouse to send input to the touch screen on the Mac, it is mapped incorrectly. See the video for details. The touch input looks like it's mapped to the upper right corner?
touchprob.zip
Running on MacBook Pro 2016 15 inch.
GPU: AMD Radeon Pro 460 (probably irrelevant here)
The text was updated successfully, but these errors were encountered: