-
-
Notifications
You must be signed in to change notification settings - Fork 182
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
Framework laptop, set VSCode to default Wayland use such that fractional scaling looks good #1655
Comments
yeah vs code is unusable for me on fw13 with 150% scale, 125% its still bad I think all thats needed is: Exec=/usr/share/code/code --ozone-platform=wayland %F to the code.desktop file at build time, feel like i almost know enough from bluebuild to make a pr |
Yeah we could override the code.desktop but we're hesitant to do this per app since there's almost always some unintended consequence or config that users might be doing. For now we recommend copying |
we should add this to the vs code docs or framework section |
This should also be solved by F41, which is about to go to beta, and then maybe we recommend :stable for framework from then on? Or someone does a PR, whichever comes first I guess, hah. |
Stumbled across this again, since VS Code is now working for the first time very nicely with Wayland support enabled, thanks to this issue being solved, where pane moving was not possible yet due to upstream Electron problem: microsoft/vscode#156723 This also fixed pane movement for Obsidian and Wayland. So from now on, I started to use fractional scaling, and it is wonderful :D I also wrote a small Ansible script to apply it to VSCode directly so dont have to do it manually for my maschines, especially when desktop launcher updates due to VSCode update :) https://github.com/frederikb96/vscode-wayland-support-enable-desktop-file |
FWIW, at Chromium side, we've worked recently on proper fractional scaling support (addressing the blurriness issues reported) which started landing since Chromium M128, behind the |
Describe the bug
I have a fresh bluefin on my framework 13 laptop. I start vscode and it looks blurry. I checked web for the issue and found this closed one here: #1362
I followed the workaround to set
ELECTRON_OZONE_PLATFORM_HINT=auto
and then it works.My request would be to set this out of the box for Framework laptops such that users dont have to check the web to find this issue and apply the workaround themselfes. Thanks :)
What did you expect to happen?
On fresh framework laptop, a non blurry VS Code :)
Output of
rpm-ostree status
No response
Output of
groups
No response
Extra information or context
No response
The text was updated successfully, but these errors were encountered: