You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Font size issue since I updated the latest version #1836
Do you have a high DPI screen/monitor? What is your 'native' resolution?
Are you running the DB Browser for SQLite, or DB Browser for SQLCipher? It appears the latter. Have you tried the former? Both .exe's are in the installed directory.
OK, Qt should be 5.11.3, but it appears you're using 5.7.1. Interesting you've updated.
Can you uninstall DB4S, then delete the directory completely, and reinstall 3.11.2 again. It looks like the update didn't update all the files...
Actually, just to confirm. When you uninstall DB4S, can you check the install directory - has it been removed, or is there a DLL floating around?
What version of DB4S were you running before?
Doh! Didn't spot the 32bit/64bit thingy. Well done! @gregzerbib - as you're on Windows 10, can you run the 64bit version? It would be surprising if you're running a 32bit version of Windows 10...
just uninstalled and installed the 64but version, and I still experience
teh same issue
I restored to default settings in preference, and still same issue
I'll try this
Can you uninstall DB4S, then delete the directory completely, and reinstall
3.11.2 again. It looks like the update didn't update all the files...
Take a look at the screenshot: I've changed the resolution of my screen, it
changes some tab names but not all of them. I think it may be due to a bug
in the code, don't you think?
LMK
Thx
Greg
[image: image.png]
The image you posted in your email didn't copy across to our support area. Can you post it directly in GitHub? #1836
As per my first message, what is your resolution natively?
Just for 'completeness', when you click on Help and About, what version of Qt does it say you're now using?
Finally, when you changed the resolution for the screenshot, what resolution did you set?
Here you go for the screenshot: I changed the resolution to 1920*1080 and the result is attached, no big change.
Native resolution: 2736*1824
version (I switched back to the previous version but it doe snot help):
Version 3.11.1
Built for i386-little_endian-ilp32, running on x86_64
Qt Version 5.7.1
SQLite Version 3.27.1
Thanks @gregzerbib. Screenshot received with thanks. I don't think the other developers have a high def monitor (as I recall a similar issue previously) but the situation might change...
I thought the newer version of Qt handled high DP monitors better, but ... obviously not.
It mentions three environment variables that are probably worth experimenting with:
QT_AUTO_SCREEN_SCALE_FACTOR
QT_SCALE_FACTOR
QT_SCREEN_SCALE_FACTORS
Are you comfortable with setting environment variables and launching programs from the Windows command line? Asking because that's probably a decent approach for investigating if any of the above variables make a difference, like in the first answer here. 😄
I don't think the other developers have a high def monitor (as I recall a similar issue previously) but the situation might change...
Maybe we should figure out the cost of a decent HiDPI monitor for @MKleusberg and/or @mgrojo, and see if we can get that funded via our Patreon account?
Our server costs were funded in 3 days, so it might be feasible. 😄
Also depends if their graphics card / development laptop / boat / other, can support that.
Where I used to work, we had a laptop that had a high res but it just sat in the cupboard as it was too high to use. Open Outlook, and everything was just too small. Damn. I should have stored it here for er, purposes....
Alas, I'm having the same issue. Menu fonts are so small since the last upgrade that they're completely unreadable. (Win 10)
Setting Windows to 150% does nothing.
I can confirm tho that setting set QT_AUTO_SCREEN_SCALE_FACTOR=1
before launching the program DOES work.
Wouldn't it be possible to include that in the GUI?
That's a decent idea. We could probably do something like that in our nightly builds, and see if it has adverse side effects for people that don't have HiDPI monitors. If it doesn't cause any issues, we'd leave it in "as-is" and this might be "fixed". 😄
Wouldn't it be possible to include that in the GUI?
I don't know how Qt works, but it depends on at what point the Qt GUI is initiated. Not sure what the very first line of DB4S code is, but if its 'set this environment variable', then /possibly/ the Qt GUI has already been set up, so setting that variable may not have the right effect... but if its persistent (ie, the environment variable isn't reset when the program is closed) it'll work on the next launch ... so might be one of those "Please restart the program to run with this flag" type option... which will be fine until Windows is rebooted...
On a side note, I assume that set command is Windows only? I assume this isn't a Windows only issue?
On another side note, I've got my paws on a laptop with a high definition screen. I'll try this on there...
There could also be problems in qss (QT style sheet) files. If the font
size is set "explicitly" in these files, which can be loaded on
QApplication object or other QWidget initialization, changing it "on the
fly" is not easy and involves usage of the "unpolish()/polish()" functions.
IIRC, QT is moving away from style sheets in Qt6.
@ilgrank With that environment variable, did you set it through Windows via a GUI (eg Control Panel or whatever Win10 uses), or manually from the command line then run DB4S?
I just run it in a command-prompt and ran DB4S, and didn't spot any weirdness (I don't have an HiDPI monitor on this particular laptop...)
As an aside, if you set an environment variable, its only for that 'session' - if you open another command-prompt, the environment variable isn't set. So DB4S will have to set this environment variable before running, and will have to test that its 'soon enough'.
@ilgrank With that environment variable, did you set it through Windows via a GUI (eg Control Panel or whatever Win10 uses), or manually from the command line then run DB4S?
I made a simple batch file:
@echo off
set QT_AUTO_SCREEN_SCALE_FACTOR=1
"DB Browser for SQLite.exe"
Reacted by Chris Locke, James Moger, Umut Sagir and Justin Clift
@echo off
set QT_AUTO_SCREEN_SCALE_FACTOR=1
"DB Browser for SQLite.exe"
In my OS Windows 10 version 21H1, I saw that it is sufficient to go into the properties of the shortcut that launches the application and in the Compatibility panel check "High DPI scaling override behavior" with Scaling performed by System (Enhanced).
@echo off
set QT_AUTO_SCREEN_SCALE_FACTOR=1
"DB Browser for SQLite.exe"
In my OS Windows 10 version 21H1, I saw that it is sufficient to go into the properties of the shortcut that launches the application and in the Compatibility panel check "High DPI scaling override behavior" with Scaling performed by System (Enhanced).
Activity
chrisjlocke commentedon Apr 4, 2019
Do you have a high DPI screen/monitor? What is your 'native' resolution?
Are you running the DB Browser for SQLite, or DB Browser for SQLCipher? It appears the latter. Have you tried the former? Both .exe's are in the installed directory.
gregzerbib commentedon Apr 4, 2019
chrisjlocke commentedon Apr 4, 2019
OK, Qt should be 5.11.3, but it appears you're using 5.7.1. Interesting you've updated.
Can you uninstall DB4S, then delete the directory completely, and reinstall 3.11.2 again. It looks like the update didn't update all the files...
chrisjlocke commentedon Apr 4, 2019
Actually, just to confirm. When you uninstall DB4S, can you check the install directory - has it been removed, or is there a DLL floating around?
What version of DB4S were you running before?
justinclift commentedon Apr 4, 2019
Our Win32 builds are still done with Qt 5.7.1, as that (in theory) means it should work on Windows XP still. 😄
Our Win64 builds are done with Qt 5.11.3.
justinclift commentedon Apr 4, 2019
Maybe doing the "Reset Preferences" thing would help?
chrisjlocke commentedon Apr 4, 2019
Doh! Didn't spot the 32bit/64bit thingy. Well done!
@gregzerbib - as you're on Windows 10, can you run the 64bit version? It would be surprising if you're running a 32bit version of Windows 10...
gregzerbib commentedon Apr 4, 2019
gregzerbib commentedon Apr 4, 2019
chrisjlocke commentedon Apr 4, 2019
The image you posted in your email didn't copy across to our support area. Can you post it directly in GitHub?
#1836
As per my first message, what is your resolution natively?
Just for 'completeness', when you click on Help and About, what version of Qt does it say you're now using?
Finally, when you changed the resolution for the screenshot, what resolution did you set?
gregzerbib commentedon Apr 4, 2019
Here you go for the screenshot: I changed the resolution to 1920*1080 and the result is attached, no big change.
Native resolution: 2736*1824
version (I switched back to the previous version but it doe snot help):
Version 3.11.1
Built for i386-little_endian-ilp32, running on x86_64
Qt Version 5.7.1
SQLite Version 3.27.1
Does it help?
chrisjlocke commentedon Apr 4, 2019
Thanks @gregzerbib. Screenshot received with thanks. I don't think the other developers have a high def monitor (as I recall a similar issue previously) but the situation might change...
I thought the newer version of Qt handled high DP monitors better, but ... obviously not.
justinclift commentedon Apr 4, 2019
Thanks @gregzerbib, that's helpful info.
It's probably (guessing here) something to do with Qt (the user interface tool kit we use) misunderstanding something about your system's display.
Looking around online, this info seems relevant:
https://doc.qt.io/qt-5/highdpi.html#high-dpi-support-in-qt
It mentions three environment variables that are probably worth experimenting with:
Are you comfortable with setting environment variables and launching programs from the Windows command line? Asking because that's probably a decent approach for investigating if any of the above variables make a difference, like in the first answer here. 😄
justinclift commentedon Apr 4, 2019
Maybe we should figure out the cost of a decent HiDPI monitor for @MKleusberg and/or @mgrojo, and see if we can get that funded via our Patreon account?
Our server costs were funded in 3 days, so it might be feasible. 😄
4 remaining items
chrisjlocke commentedon Apr 5, 2019
Also depends if their graphics card / development laptop / boat / other, can support that.
Where I used to work, we had a laptop that had a high res but it just sat in the cupboard as it was too high to use. Open Outlook, and everything was just too small. Damn. I should have stored it here for er, purposes....
justinclift commentedon Apr 5, 2019
Or donate it to someone on the Outlook team, so they have to fix it. 😉
gregzerbib commentedon Apr 5, 2019
ilgrank commentedon Jun 30, 2020
Alas, I'm having the same issue. Menu fonts are so small since the last upgrade that they're completely unreadable. (Win 10)
Setting Windows to 150% does nothing.
I can confirm tho that setting
set QT_AUTO_SCREEN_SCALE_FACTOR=1before launching the program DOES work.
Wouldn't it be possible to include that in the GUI?
justinclift commentedon Jun 30, 2020
That's a decent idea. We could probably do something like that in our nightly builds, and see if it has adverse side effects for people that don't have HiDPI monitors. If it doesn't cause any issues, we'd leave it in "as-is" and this might be "fixed". 😄
chrisjlocke commentedon Jun 30, 2020
I don't know how Qt works, but it depends on at what point the Qt GUI is initiated. Not sure what the very first line of DB4S code is, but if its 'set this environment variable', then /possibly/ the Qt GUI has already been set up, so setting that variable may not have the right effect... but if its persistent (ie, the environment variable isn't reset when the program is closed) it'll work on the next launch ... so might be one of those "Please restart the program to run with this flag" type option... which will be fine until Windows is rebooted...
On a side note, I assume that set command is Windows only? I assume this isn't a Windows only issue?
On another side note, I've got my paws on a laptop with a high definition screen. I'll try this on there...
scottfurry commentedon Jun 30, 2020
justinclift commentedon Jun 30, 2020
@ilgrank With that environment variable, did you set it through Windows via a GUI (eg Control Panel or whatever Win10 uses), or manually from the command line then run DB4S?
chrisjlocke commentedon Jul 1, 2020
I just run it in a command-prompt and ran DB4S, and didn't spot any weirdness (I don't have an HiDPI monitor on this particular laptop...)
As an aside, if you set an environment variable, its only for that 'session' - if you open another command-prompt, the environment variable isn't set. So DB4S will have to set this environment variable before running, and will have to test that its 'soon enough'.
ilgrank commentedon Jul 1, 2020
I made a simple batch file:
steforl commentedon Mar 3, 2022
In my OS Windows 10 version 21H1, I saw that it is sufficient to go into the properties of the shortcut that launches the application and in the Compatibility panel check "High DPI scaling override behavior" with Scaling performed by System (Enhanced).
unluckylukas commentedon Mar 21, 2024
This worked for me!
justinclift commentedon Mar 21, 2024
Cool, sounds like that should go into our documentation (maybe in the wiki?) somewhere. 😄
ZYinMD commentedon Jun 7, 2024
On Win11, this is what fixed it for me:
justinclift commentedon Jun 8, 2024
Interesting. That's a good tip for future people to try too. 😄