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

Wayland Support #1375

Open
00-kat opened this issue Apr 13, 2024 · 3 comments
Open

Wayland Support #1375

00-kat opened this issue Apr 13, 2024 · 3 comments

Comments

@00-kat
Copy link

00-kat commented Apr 13, 2024

TL;DR runs on Xwayland, is it possible to get it working on Wayland?

Is your feature request related to a problem? Please describe.

Currently, F3D runs under Xwayland. This means it can't fractionally scale. Note the text:
Screenshot of title in F3D
Screenshot of the axis in F3D
Also, since it can't fractionally scale, my cursor appears to be 1.5x larger than it should.
In F3D:
image
Everywhere else:
image
This is simply an X11 problem.

Describe the solution you'd like

Figure out how to use Wayland with whatever graphics library is being used (not sure if this is a Vtk problem).

Describe alternatives you've considered

  • Not do anything.
  • Lobby for Xwayland or X11 or whatever to support fractional scaling (<-- not happening).
  • If this is an issue with Vtk (which I assume does the rendering), create a feature request upstream, then wait.

Additional information

There might be some cute little command line flags or environment flags that the GUI library supports to enable Wayland. Not sure.

Contribution

Please tell us if you are able to contribute (Can you develop this new feature?)
Nope, I have no idea on anything graphics library related, except that there's a couple flags you can set for Qt, GTK and Electron apps.

@mwestphal
Copy link
Contributor

HI @cd-CreepArghhh

not sure if this is a Vtk problem

It is a VTK issue: https://gitlab.kitware.com/vtk/vtk/-/issues/17982

@00-kat
Copy link
Author

00-kat commented Apr 14, 2024

Oh right, should I close this then?

@mwestphal
Copy link
Contributor

No, this issue is still valid, it just that the "fix" (its an huge feature actually, not a simple fix) must happen in VTK at some point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Discuss
Development

No branches or pull requests

2 participants