Skip to content

Font size issue since I updated the latest version #1836

Open

Description

@gregzerbib

Details for the issue

What did you do?

I updated the software to the latest version (pushed to me today)

What did you expect to see?

not much, just the standard way it looks

What did you see instead?

the fint size is tiny, and when I try to change font size settings in the PREFERENCE menu, there is no change whatsoever

bug DB

Useful extra information

DB4S v3.11.2 [built for i386-little_endian-ilp32] on Windows 10 (winnt/10.0.17134) [x86_64]
using SQLite Version 3.27.2
and Qt 5.7.1

Activity

  1. chrisjlocke commented on Apr 4, 2019

    @chrisjlocke
    Member

    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.

  2. gregzerbib commented on Apr 4, 2019

    @gregzerbib
    Author
  3. chrisjlocke commented on Apr 4, 2019

    @chrisjlocke
    Member

    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...

  4. chrisjlocke commented on Apr 4, 2019

    @chrisjlocke
    Member

    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?

  5. justinclift commented on Apr 4, 2019

    @justinclift
    Member

    Qt should be 5.11.3, but it appears you're using 5.7.

    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.

  6. justinclift commented on Apr 4, 2019

    @justinclift
    Member

    Maybe doing the "Reset Preferences" thing would help?

  7. chrisjlocke commented on Apr 4, 2019

    @chrisjlocke
    Member

    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...

  8. gregzerbib commented on Apr 4, 2019

    @gregzerbib
    Author
  9. gregzerbib commented on Apr 4, 2019

    @gregzerbib
    Author
  10. chrisjlocke commented on Apr 4, 2019

    @chrisjlocke
    Member

    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?

  11. gregzerbib commented on Apr 4, 2019

    @gregzerbib
    Author

    bug #2

    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?

  12. chrisjlocke commented on Apr 4, 2019

    @chrisjlocke
    Member

    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.

  13. justinclift commented on Apr 4, 2019

    @justinclift
    Member

    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:

    • 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. 😄

  14. justinclift commented on Apr 4, 2019

    @justinclift
    Member

    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. 😄

  15. 4 remaining items

  16. chrisjlocke commented on Apr 5, 2019

    @chrisjlocke
    Member

    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....

  17. justinclift commented on Apr 5, 2019

    @justinclift
    Member

    Or donate it to someone on the Outlook team, so they have to fix it. 😉

  18. gregzerbib commented on Apr 5, 2019

    @gregzerbib
    Author
  19. ilgrank commented on Jun 30, 2020

    @ilgrank

    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?

  20. justinclift commented on Jun 30, 2020

    @justinclift
    Member

    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". 😄

  21. chrisjlocke commented on Jun 30, 2020

    @chrisjlocke
    Member

    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...

  22. scottfurry commented on Jun 30, 2020

    @scottfurry
    Contributor
  23. justinclift commented on Jun 30, 2020

    @justinclift
    Member

    @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?

  24. chrisjlocke commented on Jul 1, 2020

    @chrisjlocke
    Member

    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'.

  25. ilgrank commented on Jul 1, 2020

    @ilgrank

    @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"
    
  26. steforl commented on Mar 3, 2022

    @steforl
    @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).

  27. unluckylukas commented on Mar 21, 2024

    @unluckylukas
    @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).

    This worked for me!

  28. justinclift commented on Mar 21, 2024

    @justinclift
    Member

    Cool, sounds like that should go into our documentation (maybe in the wiki?) somewhere. 😄

  29. ZYinMD commented on Jun 7, 2024

    @ZYinMD

    On Win11, this is what fixed it for me:

    image
    image

  30. justinclift commented on Jun 8, 2024

    @justinclift
    Member

    Interesting. That's a good tip for future people to try too. 😄

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions