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

Application font should default to Segoe UI for Windows Vista and above with themes enabled #4511

Closed
Quppa opened this issue Feb 22, 2018 · 0 comments

Comments

@Quppa
Copy link
Contributor

Quppa commented Feb 22, 2018

Do you want to request a feature or report a bug?
Feature

What is the current behavior?

  • The default application font for Windows Vista and above with themes enabled is Tahoma.
  • The default fixed width font is Courier New.
  • Fonts within the app are inconsistent in places (hard-coded to Segoe UI, etc.).
  • The first-load language selection dialog content overflows available space when Segoe UI is set as the default font.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

  • Delete GitExtensions.settings and load the application. Note the default fonts in Settings.

What is the expected behavior?

  • The default application font for Windows Vista and above with themes enabled should be Segoe UI. It should still be Tahoma for Windows 7 and below when themes are disabled (for Windows 8 and above it should always be Segoe UI). SystemFonts.MessageBoxFont calculates the appropriate value for us.
  • Consolas should be the default fixed-width font, replacing Courier New.
  • The application should reliably respect the application font setting.
  • The first-load language selection dialog content should fit within the window frame.

Environment you encounter the issue:

  • GitExtensions version: 2.51
  • GIT version: 2.16.2
  • OS version: Windows 10 1709 16299.248

Did this work in previous version of GitExtensions (which)?
No.

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

Successfully merging a pull request may close this issue.

2 participants