Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

FF has crisp(ish) and clear fonts. Atom editor/GUI has went throuh PS's blur filter. #17502

Open
1 task done
Personwithhat opened this issue Jun 12, 2018 · 9 comments
Open
1 task done

Comments

@Personwithhat
Copy link

Personwithhat commented Jun 12, 2018

Prerequisites

Description

Entire atom GUI and editor blurry. Blurry fonts, blurry editor. Similar issues in VStudio.

Steps to Reproduce

  1. Download newest release from base page
  2. Have LCD screen (DirectWrite issue?..)

Expected behavior: [What you expect to happen]
Readable text. FF for me is pretty sharp.

Actual behavior: [What actually happens]
Blurry screen everywhere.

Reproduces how often: [What percentage of the time does it reproduce?]
100%

Versions

Newest.
Windows 10 x64 pro home, newest again.

Additional Information

LCD Screen 2560x1400p, at 120hz
AMD Radeon 7970
ClearType enabled
Have attempted many different atom startup flags, DPI scaling 'fixes', etc.
Using standard 100% DPI scaling, I don't use 125%+ etc.
Plenty of themes/fonts tried, did not solve. Nearly bricked computer with MacType xd

Any solutions would be stellar. Someway of changing to different antialiasing? No option I've done works etc.
FF could be better but the editor is hands-down horrible.
editorblurry

@steveward
Copy link

Thanks for opening this @Personwithhat. I have a very similar machine (Radeon 7950, Windows 10 Pro, 1440 display), but I am not able to see the same blur issues (granted my eyes aren't great to begin with).

Have you tried using the --force-device-scale-factor=1 and high-dpi-support=1 flags to see if they help at all? I know you mentioned you tried a number of flags, but I just want to make sure we are covering all of our bases.

@Arcanemagus
Copy link
Contributor

@Personwithhat could you clarify what version of Atom you are using? "Newest" could mean any of 3 different things right now, and as soon as a new version is released it will mean something different 😉.

You can get this information from copy and pasting the output of atom --version and apm --version from the command line.

@the-j0k3r
Copy link

@Personwithhat Are those entries on the screenshot left side part of the style.less?

Ide like to see a screenshot without any of those entries shown (commented out) those text stroke entries wouldn't help but maybe even help cause this.

@Personwithhat
Copy link
Author

Personwithhat commented Jul 12, 2018

@steveward Yea I've tried all of that

@Arcanemagus 1.27.2 is the verison

@the-j0k3r I've deleted all of them and added them, nothing changes ofc.

On a side note, windows died on me so I reinstalled a completely fresh system (same hardware)

Isuse still persists .-.

@ozra
Copy link

ozra commented Nov 10, 2018

I will comment here, and in other issues I find matching, in an attempt to provide some insight:

  • Font rendering has been blurry in Atom since I started using it, probably 2015, possibly earlier.
  • Expectation: be a clear as Sublime, or any other program
  • Can confirm I've also tried all the kinds of style-tricks as shown above, multiple times, every few months I go through trying things out again. No change with any update so far :-(.
  • Have also tried all tips for command-line parameters I've come across from different forums, since 2015-ish, no change
  • OS, from initially Ubuntu 15-ish, to currently 18.10
  • machines have been ASUS with lofi GFX to currently ASUS with Nvidia GTX 1060
  • Same blurry anti-alias through all that
  • Optimally it should be possible to render raster-fonts without anti-alias, for my taste, but any improvement would make my day

Crystal clear font rendering is fundamental for a tool which primary purpose is interacting with text!

We all have one pair of eyes! The font-rendering issue really should have top priority imho.

@Personwithhat

This comment has been minimized.

@stale
Copy link

stale bot commented Nov 16, 2019

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. Because the Atom team treats their issues as their backlog, stale issues are closed. If you would like this issue to remain open:

  1. Verify that you can still reproduce the issue in the latest version of Atom
  2. Comment that the issue is still reproducible and include:
    • What version of Atom you reproduced the issue on
    • What OS and version you reproduced the issue on
    • What steps you followed to reproduce the issue

Issues that are labeled as triaged will not be automatically marked as stale.

@stale stale bot added the stale label Nov 16, 2019
@Personwithhat
Copy link
Author

Personwithhat commented Nov 18, 2019

Still reproducible. Steps same as above, and in new version.

Obviously not the only person to have this issue.

@stale stale bot removed the stale label Nov 18, 2019
@stale
Copy link

stale bot commented Dec 25, 2020

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. Because the Atom team treats their issues as their backlog, stale issues are closed. If you would like this issue to remain open:

  1. Verify that you can still reproduce the issue in the latest version of Atom
  2. Comment that the issue is still reproducible and include:
    • What version of Atom you reproduced the issue on
    • What OS and version you reproduced the issue on
    • What steps you followed to reproduce the issue

Issues that are labeled as triaged will not be automatically marked as stale.

@stale stale bot added the stale label Dec 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants