-
-
Notifications
You must be signed in to change notification settings - Fork 319
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
issues with X and Y scaling with 90degree rotation of tablet #2930
Comments
|
Do not use your DE's settings for tablets, those interfere with OTD's mapping as you have pointed out and there's no way for OTD to correct for such changes. Do everything inside OTD. |
respectfully @X9VoiD this is not true - OTD accepts the monitor layout as provided (and configured by) the desktop environment. The DE does this, in all cases, prior to OTD being involved in anyway. This is why OTD displays the (DE configured) monitor layout in the upper pane. In my case, the only config I have done is setting how my monitors are physically laid out. Of course this step is unavoidable. And the only reason I include anything about DE configuration is to demonstrate what is working. If you'd like, just pretend I opened the bug at step6 diretly: here is my screen, there's a bug, or there is something I am doing wrong in OTD. Also, per directions/FAQ, all the data in this issue takes place after following the FAQ, including blacklisting
|
i think i have narrowed down the bug by experimentation.
Lock to usable area incorrectly truncates the width/height's entered. The height field displays the intended value, but the visual (and apparently the model that's used internally) has truncated it. Shall I submit a new bug that zeros in on this, or can this bug work for the team? |
here's how I found/worked-around this bug: |
|
finally, to summarize what a fix would accomplish for this:
|
Duplicate of #1143 |
Folks - no, it's not a duplicate of #1143 which deals with changes in monitor layout (eg DE, above/outside OTD) My issue is 100% within OTD, and it requires ZERO interactions with DE-level settings, or monitor changes. Obviously my OP has some DE monitor config - because at that time I obviously had no idea where the bug was, and I was trying to show what worked, what seemed wrong ... (and all quite painstakingly broken down / summized / screenshoted to make it digestible by the team) Again - this bug has nothing to do with DE changes. To quote #2930 (comment):
Shall I just open a new bug starting at #2930 (comment)? |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, the issue is really really long and difficult to keep track of what the issue actually is. I tried setting up a rotated monitor and saving settings for that, and it seems to perfectly center when starting OTD. Here is what OTD's settings looks like for me: This smells more like a combination of #2573 #2594 than anything else, as well as using your DE's settings. If you can reproduce this in a default WM it is more likely your bug is able to be reproduced. |
Steps to Reproduce
see comments - this is actually a bug in how rotated coordinate system is applied inconsistently in the UI; after the root cause leads to the wrong Tablet geom being used, the scaling issue just follows from those incorrect geometries. Do I need to submit a new bug, or can this be re-opened?
connect a graphics tablet to your PC. Follow steps 1-6 (see detailed annotated graphics below for what I see). For all we're connecting the tablet as a 2nd monitor, "extending" the desktop (vs mirroring, or overlaying/overlapping the tablet on the existing screen(s)
Expected Behavior
I should be able to easily set my tablet up in portrait, just as it works in landscape in bullets 1-3
Observed Behavior
for completeness, these are as expected:
but then it all falls apart in portrait:
Tablet Device
huion kamvas 12 over usb-c alt mode
Diagnostic Information
says too long; will add as comment below
Acknowledgements
The text was updated successfully, but these errors were encountered: