• src/sbbs3/ctrl/AboutBoxFormUnit.dfm ClientFormUnit.dfm ConfigWizardUni

    From Rob Swindell (on Windows 11)@1:103/705 to Git commit to main/sbbs/master on Wed Sep 27 18:53:49 2023
    https://gitlab.synchro.net/main/sbbs/-/commit/275155a2d621f0d869924fce
    Modified Files:
    src/sbbs3/ctrl/AboutBoxFormUnit.dfm ClientFormUnit.dfm ConfigWizardUnit.dfm CtrlPathDialogUnit.dfm EventsFormUnit.dfm FtpCfgDlgUnit.dfm FtpFormUnit.dfm LoginAttemptsFormUnit.dfm MailCfgDlgUnit.dfm MailFormUnit.dfm MainFormUnit.dfm NodeFormUnit.dfm PreviewFormUnit.dfm PropertiesDlgUnit.dfm ServicesCfgDlgUnit.dfm ServicesFormUnit.dfm SoundCfgDlgUnit.dfm SpyFormUnit.dfm StatsFormUnit.dfm StatsLogFormUnit.dfm TelnetCfgDlgUnit.dfm TelnetFormUnit.dfm TextFileEditUnit.dfm UserListFormUnit.dfm UserMsgFormUnit.dfm WebCfgDlgUnit.dfm WebFormUnit.dfm
    Log Message:
    Fun (not) with fonts

    Running SBBSCTRL on Windows 11 with a 4K monitor looked horrible.
    The default font sizes varied widely - I'm not sure why this wasn't
    apparent before now. And the default font ("MS Sans Serif") is no longer included in modern Windows versions, so when choosing a Log font, the pre-selected font was just blank. So change use of "MS Sans Serif"
    everywhere to "Microsoft Sans Serif" which appears to have been around since Win95 and be the preferred alternative. I would consider Segoe, but that
    wasn't introduced into Windows until Vista and I'm not sure (yet) what
    troubles that might introduce. I'll experiment with a WinXP VM maybe
    and find out.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)