Skip to content
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

Resolution issue #1

Open
stoddabr opened this issue Oct 29, 2020 · 5 comments
Open

Resolution issue #1

stoddabr opened this issue Oct 29, 2020 · 5 comments

Comments

@stoddabr
Copy link

Hi, not sure exactly where in the repo to put this so I'm putting it in the base.

It's still usable but I found obviously a GUI layout issue while running the windows executable

Just started working with this kit and there was an issue with the Syntacts Windows UI. I think this issue is caused by the surface pro having a weird screen resolution setup because I've had similar issues with other window executable UIs (mostly older software if that helps).

Running on:

  • Windows 10 Pro x64 version 10.0.18363 Build 18363
  • Surface Pro (2017 5th generation I think?)
  • 2736 x 1824 display at 200% (recommended) scale

screenshot of my entire screen
image

@stoddabr
Copy link
Author

Just watched the iROS presentation btw, great job!

@epezent
Copy link
Member

epezent commented Oct 29, 2020

Thanks for letting us know! We will need to address DPI scaling to solve this issue.

In the meantime, I believe windows allows you to disable DPI scaling on a per-app basis:
https://support.microsoft.com/en-us/help/3025083/windows-scaling-issues-for-high-dpi-devices

Can you give that a try?

@epezent
Copy link
Member

epezent commented Oct 29, 2020

I just tested on 2560x1440p display @ 200% scaling. My window did not have any black area like yours, but the UI did not scale correctly (it was quite small). I've implemented DPI awareness in an another application before, so I should be able to resolve this relatively soon. Hang tight.

@gadzooks00
Copy link
Member

@epezent Has this update already been resolved?

@epezent
Copy link
Member

epezent commented Aug 17, 2021

No it never happened. I would deprioritize this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants