-
Notifications
You must be signed in to change notification settings - Fork 344
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
(Bug): Mouse pointer is not aligning/is offset with graph in ColorLookup Node #971
Comments
Probably a hidpi issue? Does it work if scaling 100%? Also note that the Qt5 version of Natron still has some UI issues compared to older versions (Qt4). |
I tried zooming in and out of the graph if that's what you mean and still have the problem. Is this what you meant by scaling being 100%? Do you think it's worth downloading an older version of natron? |
No, I meant display/monitor scaling. My theory is that we don't offset position X/Y with the current dpi value (or do it wrong). |
Ah right I see - I tried different monitor resolutions and it doesn't help. Do you think using an external monitor would fix this? |
Thanks for testing. Hmm, might be something else. I can test on a Mac tomorrow.
If 100% scaling on your primary monitor don't work it will probably not work on other monitors. |
Ok thanks! Makes sense |
Make sure to follow our issue report guidelines
Natron version
Natron 2.6
Operating system
macOS Sonoma 14.1.2
System specs
128GB Apple M3 Max
Did you install Natron using the official installer?
Custom installation path
No response
What were you trying to do?
I was trying to use the graph in the colorlookup node however the mouse pointer is offset from what's selected in the graph so i have to click in a different location to where it should select. It's incredibly tricky to adjust colour values this way.
I tried this on a windows machine and did not have this issue.
Have tried restarting natron / computer and the issue still persists.
Let me know if you need any more info.
Thanks,
What did you expect to happen? What happened instead?
Step-by-step reproduction instructions
Additional details
This issue does not happen in a windows machine
The text was updated successfully, but these errors were encountered: