1. Stefan B Avatar Stefan B
  2. nina
  3. NINA
  4. Issues

Image History: Font unreadable

Issue #739 closed
Ruediger created an issue

Hi Stefan,

changing the font in image history rendered it almost unreadable and is extremely hard to read. The fuzziness is extremely irritating, since while reading the eyes try to focus the text, but they cannot. This is very tedious and not ergonomic at all. You feel like being drunken 😉

Please bring back old style or at least a possibility to switch it off in options.

Thanks a lot and Merry Christmas!
Rüdiger

‌

Comments (26)

  3. Ruediger reporter

    Hi Stefan,
    A happy new year 🙂

    Can you please take care about this issue in one of the very next releases? This font is causing actually a head-ache like not wearing glasses though you should. It is painful.
    Many thanks in advance!

    Rüdiger

  4. Stefan B repo owner

    While i don’t experience the pain that you do, by reading this, I do agree that it makes it hard to read. I will check for a different solution.

  7. Ruediger reporter

    Hi Stefan,
    since red on dark has only very little contrast I cannot judge whether this is better or not.
    Why not simply a sharp and crispy font? There is absolutely no need to make it fuzzy there - the only place.
    Or integrate an option to configure it or remove all text completely. This fuzziness drives me really crazy when working with it. You get eye cancer. 😞

    Cheers
    Rüdiger

    ‌

  9. Ruediger reporter

    Does not help at all, since background is usually black. Sorry, this is unreadable for me.
    But no problem. I will disable the window and use external viewer.

  10. Stefan B repo owner

    If you can’t read it there you can’t read it anywhere else. It is using the standard app font with the standard background you are setting. What is the problem with that.

  12. Ruediger reporter

    No, the only window where it is fuzzy is this window. I have absolutely no problem in any other areas or window. Just have a look on my screen shot attached above. There you can see that all other text is crispy and sharp, Only the text blended over the images is so fuzzy you almost cannot read it. This is not an problem of jpg. Its is so blurry here.

    The character can not be recognized. I really do get head ache when have this window opened. I had to close it. The human eye/brain always tries to recognize patterns and tries to match. This it does until it gets a solution. If it cannot succeed it is a problem for it. To make important information fuzzy in a GUI is not a good idea in general and does not follow any barrier free or good UX concepts. To make text fuzzy in any way is a bad idea.

  14. Ruediger reporter

    Sorry, no, The page was not refreshed, since I was typing.

    A little bit better, but still (too) poor to read.
    I see no reason why to blur it. What is the idea behind to to do so?

  15. Stefan B repo owner

    I don’t get what you mean by blurring. This screenshot shows the exact same font and coloring as the whole rest of the app. Maybe it’s the jpg compression, but other than that it is identical.

  16. Ruediger reporter

    no, it is png.

    I have attached a second screenshot which show the difference. The blue text appears completely fuzzy and blurred, whereas the rest clear readable. Magnification is 3x.
    Also when looking at the complete GUI everything is easy to read an crispy, but the image history is fuzzy. Unfortunately due to shrinking the image in size it is less visible in the screenshot, but life it is significant.

    ‌

  17. Stefan B repo owner

    Your Screenshot is showing the old Version, which we already discussed that it was not good.

  18. Ruediger reporter

    Only very little improvement and a significant difference in readability between standard text and image history text.

    ‌

  19. Stefan B repo owner

    The Text is using the standard Textblock. Code is exactly like before the Change that introduced the outlining with the addition of a background. No custom Font, Blur or fuzzy Option enabled.

    It might be rendered differently by WPF due to sitting in a different parent element but it was Like that earlier too.

  20. Stanley Dimant

    Possible this happened due to bitmap caching - the font is getting rendered differently. Worth a try to adjust but it’s incredibly minor.

  21. Ruediger reporter

    Thanks for investigating. But as you see, there is a difference.
    But ok. It is better than before. I think this also helps Jim who had also problems. I can also life with that.

    Many Thanks!

  23. Stefan B repo owner

    @Stanley Dimant looks like the bitmapcache is indeed responsible for the slight blur. I’ll remove that again, too.

  27. Log in to comment
Assignee
–
Type
bug
Priority
major
Status
closed
Component
User Interface
Version
–
Votes
1
Watchers
1
Jira: the preferred issue tracker for Bitbucket. Join the team!