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

Graph window - Markings of the periods on the graph are unreadable #8632

Closed
LC-Zorg opened this issue Jan 31, 2021 · 0 comments · Fixed by #8732
Closed

Graph window - Markings of the periods on the graph are unreadable #8632

LC-Zorg opened this issue Jan 31, 2021 · 0 comments · Fixed by #8732

Comments

@LC-Zorg
Copy link

LC-Zorg commented Jan 31, 2021

Version of OpenTTD

20210114-master (applies to change #8557)

Expected result

Markings are legible and unambiguous. A glance at the graph is enough to see the period to which the value relates.
zzg 07

Actual result

Marking is very faint. In addition, the manner of markings makes them ambiguous.
zzg 01

Solutions

It is not necessary, 1 point alone will improve a lot, but the best effect in my opinion will be a combination of all points.

  1. Changing the size of the default small font - taking into account the current average resolution of monitors, it would be advisable to change it to a slightly larger one. Here, however, there is a problem with the size of the station labels, which for most fonts become larger than for the default medium font.
  2. Changing the way of marking periods - instead of abbreviations of month names, you can use Roman letters for marking quarters. It is a frequently used solution, definitely more readable and, above all, much more logical.
  3. Extension of auxiliary lines - so that they separate the symbols of periods; the lines separating the years would be slightly longer than those separating the quarters
  4. Highlighting the lines separating the years with a different shade - in the case of a dark background it would be a color one shade lighter than the other auxiliary lines.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant