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

UX: Unread article count hard to read #1725

Open
asmaloney opened this issue Jan 22, 2024 · 3 comments
Open

UX: Unread article count hard to read #1725

asmaloney opened this issue Jan 22, 2024 · 3 comments

Comments

@asmaloney
Copy link

Describe the bug

With the latest release (3.9) the unread article indicator has changed and it's a lot more difficult to read because of low contrast.

I don't have a screenshot from pre-3.9, but the numbers stood out more.

For those of us with poorer eyesight, having some colour/contrast would be very helpful here.

Some things to try:

  • making the number bold and actually black (my preference)
  • changing the "bubble" to something which stands out more from the background (e.g. a light cyan)
  • getting rid of the bubble so the number has greater contrast with the background.

Screenshots

Screen Shot 2024-01-22 at 10 11 41 AM

Please complete the following information:

  • Version 3.9.0 :7ad9df044: (8175)
  • e.g. macOS 12.7.2

Thank You

Thanks for the great app!

@Eitot
Copy link
Contributor

Eitot commented Jan 22, 2024

Have you tried using "Increase contrast" in the accessibility section of system settings?

The unread count is using a standard AppKit component. The font is also emboldened already.

@liamgreenwood
Copy link

liamgreenwood commented Jan 28, 2024

It may be using a standard component but it is materially harder to read than in the 3.8 series. Are you saying that Vienna wasn't using a standard component prior to 3.9? Sending people to system wide assessibility setting to fix a change to one application seems unnessessarily heavy handed.

@Eitot
Copy link
Contributor

Eitot commented Jan 30, 2024

Sending people to system wide assessibility setting to fix a change to one application seems unnessessarily heavy handed.

It was merely a suggestion. Since it is using the components as other apps, notably Apple Mail, I assume that the issue cannot just be with Vienna. The system setting does have the advantage that it improves legibility across the system.

Are you saying that Vienna wasn't using a standard component prior to 3.9?

It was not. The older code relied extensively on custom drawing. It was probably originally made to look like Apple Mail. The code itself needed to be replaced, because Apple changed the way table views are constructed/drawn and the code became hard to maintain and fix.

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

No branches or pull requests

3 participants