-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[Bug]: Huge font #3042
Comments
Hi @oliversen . |
@chrisjlocke, the problem is not solved. Changing the font settings didn't help. |
That's weird.. Why not try a nightly builds? |
OK. DB4S can only get its settings from the registry. Can you open regedit and rename the 'Computer\HKEY_CURRENT_USER\SOFTWARE\sqlitebrowser\sqlitebrowser' leg to something else (prefix it with an X or something).
Can you run a command prompt and type
You can then drag that 'set.txt' file into here to attach it. Renaming the registry legClose DB4S. Right click on the 'sqlitebrowser' leg and click 'Rename'. Prefix the text with an x and press [Enter]. Restart DB4S. Reverting the editAfter restarting DB4S, a new 'sqlitebrowser' leg would have been created. Press [F5] in regedit to show the new leg. Click on this new leg and press the [Delete] button. Click 'Yes' on the prompt to delete the key. |
@chrisjlocke Thanks for your help, problem found! It lies in the Tahoma font, which Sqlite Browser cannot display correctly in Windows 10. I have Tahoma listed in "HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics" for display in the OS instead of the standard Segoe UI. Interestingly, there are no problems with Tahoma in Windows XP... |
Thanks for reporting back. |
What did you do?
I opened DB Browser for SQLite
What did you expect to see?
What did you see instead?
DB Browser has a huge font. I've checked the font scaling and its on 100%. My monitor resolution is 1280x1024.
I experimented with three environment variables:
But it didn't work
.
DB4S Version
3.12.2
What OS are you seeing the problem on?
Windows
OS version
Windows 10
Relevant log output
No response
Prevention against duplicate issues
The text was updated successfully, but these errors were encountered: