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

blurred / obscured values on time-bar #2259

Closed
musikBear opened this issue Aug 13, 2015 · 7 comments
Closed

blurred / obscured values on time-bar #2259

musikBear opened this issue Aug 13, 2015 · 7 comments

Comments

@musikBear
Copy link

These are quite difficult to read. I dont believe this has been an issue before? Have the tickmaks been changed?
grimmetal

@michaelgregorius
Copy link
Contributor

This should be fixed as part of pull request #2222. On my system it looked even worse because only the bottom of the numbers was shown:
timeline-bottom

@unfa
Copy link
Contributor

unfa commented Aug 16, 2015

Maybe the vertical lines indicating bar boundaries should be drawn in bigger intervals when the session is zoomed out? It's a common practice for drawing grids in programs like Blender or Inkscape.

bars
bars1

The numbers are displayed in proper spacing, the lines should follow that - in essence - draw only lines corresponding to the drawn numbers.

@musikBear
Copy link
Author

@unfa yes, that could be a way, but then i feel that mouse-over should show precise pos. -But
Then we have a cpu eater, and that would be a catastrophe -so mouse-over is b a d
But from a moles 'view'point -the values should be more contrasting in respect to the background. It will be interesting to see what 2222 fix

@unfa
Copy link
Contributor

unfa commented Aug 16, 2015

Maybe a subtle black rectangle behind the number text would add extra contrast and increase readability?

@ghost
Copy link

ghost commented Aug 27, 2015

Adding shadow to the text may increase readability.

@zonkmachine
Copy link
Member

timebar

This looks much better now.

@Umcaruje
Copy link
Member

True. This issue was fixed. Closing.

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

5 participants