Probably fixes #7017.
Merges fine into master and 0.12.
Probably fixes #7017.
Merges fine into master and 0.12.
utACK for 0.12 (rc2) not sure if we want this for master/0.13 or if we should look for a better/alternative solution.
Build to test should be ready soon: https://bitcoin.jonasschnelli.ch/pulls/7364/
Thanks for the binaries.
Even though this is ugly, I'd say it should be merged into master as well. Lacking a better solution, it doesn't make things worse and backports easier.
Why are we not using QFontInfo(fixedFontInfo).pointSize() here?
Seems like QFont() has the same problems? Makes more sense to scale fixedFontInfo than to scale some other font's default size. Besides, we got that Qt5 thing since then?
Makes more sense to scale fixedFontInfo than to scale some other font's default size
Previously we had a "default font", so that's the reference. Though, you are welcome to change that.
Besides, we got that Qt5 thing since then?
Doesn't change anything for Windows or Linux. Only a different font for OS X.
Oh no, not more monospace related code changes. When are you guys going to give this up :-)
Tested ACK fa6a59dd397e62e850fc57df05cd6d117fbdcd82. This is a quick and stable workaround and we should backport this to 0.12. For 0.13 we need a better solution.
Current Master (to small on windows): <img width="620" alt="bildschirmfoto 2016-01-22 um 09 39 07" src="https://cloud.githubusercontent.com/assets/178464/12506086/a30392a0-c0ec-11e5-979e-04377b914084.png">
Current 0.11 version, non pretty, non mono (people are use to this font size): <img width="670" alt="bildschirmfoto 2016-01-22 um 09 41 02" src="https://cloud.githubusercontent.com/assets/178464/12506093/b067969e-c0ec-11e5-90ac-2daf36261565.png">
This PR: <img width="612" alt="bildschirmfoto 2016-01-22 um 09 38 12" src="https://cloud.githubusercontent.com/assets/178464/12506098/bd7b481c-c0ec-11e5-941a-abb18f8d5f97.png">
I don't think this solution is acceptable in the longer term. We have to do one of these:
Milestone
0.12.0