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
nvda.exe icons are awful #355
Comments
Comment 1 by jteh on 2011-01-18 06:09 |
@feerrenrut, any thoughts? Do you see this problem? |
In windows 10 I haven't noticed a problem. The start menu, the task bar, and the system tray all have the icon looking as expected. When testing with high contrast mode I dont notice any issue. However when NVDA is pinned in the start menu (thus much larger) AND my DPI is set to 175% I can notice a few rough edges. But I have to look pretty closely to notice this. I would say its acceptable even in this case. @Qchristensen What are your thoughts on this, have you noticed any icon issues? |
We are considering updating the icons for NVDA. We dont think that any of the current issues require an immediate fix, and when new icons are introduced we will try to ensure that none of these issues persist. Closing as won't fix. |
Reported by timeless on 2009-07-03 09:17
w7 rc; NVDA 0.6p3.2
The image http://www.nvda-project.org/chrome/site/images/nvda_100x100white.png looks reasonably good, but for some reason it seems like someone tried very hard to pixelate the icon when they created the icons for NVDA.exe
http://msdn.microsoft.com/en-us/library/ms997636.aspx
http://msdn.microsoft.com/en-us/library/aa511280.aspx
http://www.axialis.com/tutorials/tutorial-vistaicons.html
There seems to be an icon with resolutions up to 48x48, but it's very rough. I'm assuming that there's a vector original, it should be possible to use it to generate better icons.
Also note that as far as w7 is concerned, NVDA.exe doesn't have any icons at all -- If I manually try to change the icon of NVDA's shortcut to use NVDA.exe for an icon, it says there aren't any.
The text was updated successfully, but these errors were encountered: