-
Notifications
You must be signed in to change notification settings - Fork 466
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
Resize RenderWidget properly when using different DPI scaling. #1263
Resize RenderWidget properly when using different DPI scaling. #1263
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the long delay. rviz didn't have an active maintainer for a while...
I need to find a high-dpi display to test this 😉, but otherwise looks reasonable.
+1 on this. I have a HiDPI mac and have this issue with RViz2 in ROS. It would be great if this was merged and added to the ros 2 repo also. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have a similar issue as #1262 on a Linux(debian 9). This fix is able to fix the issue if pixel_ratio_ is kept as double.
So all the requested changes have been made and everything seems to work as expected. I can't help the ABI change without making a global variable. |
Any progress on merging this? |
I just manually applied tese patches. I really need them... So a merge would be very good. But I noticed when using these patches together with jsk-visualization and overlay-menu that the menu was not placed in the middle. The rest of the things seems to work. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These changes should be reflected in the latest commits.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rhaschke Sorry to leave these changes dangling like this. I have made all of the necessary changes in the recent commits but I do not know how to close out these changes you have requested me to review and I feel like it's the last thing keeping the PR from being merged?
I would really like to validate those changes before merging. Could anybody (maybe @sippeyxp) hint me at instructions on how to set up a high-dpi monitor on Linux (Ubuntu) to @tompe17, could you please elaborate more on the issue described in #1263 (comment)? |
@rhaschke what kind of monitors do you have access to? |
I just have a laptop (1920x1080) with an external monitor (1920x1200). But I guess, by configuring it somehow, I can pretend that the monitor is high-dpi (resulting in huge fonts / gui elements on that screen), right? So my questions is: How do I configure it like this? |
Should be able to do it in Ubuntu display settings... unless it knows the resolution and only offers scaling for hidpi. In that case maybe you could try a vm with custom display settings? |
I don't get high-dpi display settings offered. |
@rhaschke https://askubuntu.com/a/960041/73160 does this help ? |
Verified the patch fixed issue in my build (lunar). Builds fine and looks perfectly on 3840x2160 15" display. Not sure why the cont. integration is not happy. |
I don't know if you can trick the high DPI checking in QT without having the physical pixels. Let me know if @VictorLamoine 's link works for you. Thanks for checking. The CI is unhappy due to the change to the header |
The issue I saw was that an overlay menu that is centered on low resolution devices seemed to be centered in the top left 1/4 of the high resolution screen. But thing still works so do not let this block the patch. The alternative is that it does not work at all. |
I managed to have a custom pixel ratio via: |
Can this be merged into melodic-devel also ? |
It is already forward-ported (1342d2e) and released into Melodic. Are there any open issues in Melodic? |
Hi, I hope this reaches the right people :D I printed the stack-trace every time my plugin is initialized to find the problem:
|
Sorry @Tacoma, but I can't reproduce your issue. For me the stack trace looks like this:
Looks like you are creating a new VisualizationFrame in a plugin? |
See #1262 for details.