Page 2 of 3
Re: Ctrl+wheel does not work on a fresh ini
Posted: 2024-10-28, 08:34 UTC
by ghisler(Author)
You are right, it also looks more similar to Consolas than Arial. I will use Verdana if available, otherwise Arial if available.
Re: Ctrl+wheel does not work on a fresh ini
Posted: 2024-10-30, 20:52 UTC
by petermad
I have a problem with the new default settings.
I like to continue using the old default fonts for ANSI and ASCII.
It is no problem for ANSI - I can just manually set it to: Fixedsys 9 pt (Fixedsys, -12)
But I cannot get it to look the same as before for ASCII.
Before it looked like this for ASCII with default font:
https://tcmd.madsenworld.dk/listerdefaultasciiold.png
Even before TC 11.50b4 when clicking the [ ... ] button for ASCII in Lister's configuration TC automatically chose: Terminal 9pt (Terminal, -12,255) - but that does NOT look like the default font - it looks like this:
https://tcmd.madsenworld.dk/listerterminalascii.png
If I choose the size one step larger Terminal 12pt (Terminal, -16,255) it look like this:
https://tcmd.madsenworld.dk/listerterminal12ascii.png -
not satisfactory either!
And those two settings (Terminal, -12,255 and Terminal, -16,255) looks the same in TC 11.50b4
So the question is: how do I get the look of ASCII default font (
https://tcmd.madsenworld.dk/listerdefaultasciiold.png ) back in TC 11.50b4?
Would it be possible with a setting in the [Lister] section:
UseOldDefaultFonts=1
After using TC for more than 30 years, I have grown accustomed to those fonts
Re: Ctrl+wheel does not work on a fresh ini
Posted: 2024-10-31, 08:55 UTC
by ghisler(Author)
The older versions called GetStockObject(OEM_FIXED_FONT). I thought that this was using Terminal, but strangely Terminal is missing the right font size. I will add a checkbox for the old default fonts to the Lister configuration dialog.
Re: Ctrl+wheel does not work on a fresh ini
Posted: 2024-10-31, 14:15 UTC
by petermad
I will add a checkbox for the old default fonts to the Lister configuration dialog.
Great
Re: Ctrl+wheel does not work on a fresh ini
Posted: 2024-11-05, 12:08 UTC
by Usher
2
MaxX
Verdana is not the best choice. For me default variable font should be either the same one as used by TC GUI or the same one as used by Windows GUI. Otherwise it's just inconsistent.
What is more, Verdana is not as universal as other fonts. In my case Verdana contains only 951 glyphs while Tahoma contains 3419 glyphs and DejaVu Sans contains 6253 glyphs.
2
ghisler(Author)
ghisler(Author) wrote: 2024-10-27, 09:26 UTC
I found out that on NT based systems, all fonts work as OEM when setting the font family to OEM.
It's not done automatically for languages using other codepage than windows-1252 (Western). See my comment in another topic:
viewtopic.php?p=463160#p463160
Re: Ctrl+wheel does not work on a fresh ini
Posted: 2024-11-06, 08:51 UTC
by ghisler(Author)
same one as used by TC GUI
Which one? TC uses Segoe UI for the main window (also in file lists) and Microsoft Sans Serif for dialog boxes.
Re: Ctrl+wheel does not work on a fresh ini
Posted: 2024-11-06, 11:18 UTC
by Usher
2ghisler(Author)
Font for the main window (whatever it's set by the user). Some users set bolder font for file lists as it's smaller size used there.
In the case of Segoe UI I would use also Segoe UI Mono for monospaced font.
Re: Ctrl+wheel does not work on a fresh ini
Posted: 2024-11-06, 17:51 UTC
by MaxX
2
Usher
What is Segoe UI Mono?
I don't have it in W10 with latest updates:
https://i.imgur.com/Exeqc5u.png
Re: Ctrl+wheel does not work on a fresh ini
Posted: 2024-11-06, 19:31 UTC
by petermad
I don't have it
Me neither
Re: Ctrl+wheel does not work on a fresh ini
Posted: 2024-11-07, 08:05 UTC
by Horst.Epp
2Usher
There is no Segoe UI Mono under an actual Windows 11 24H2
Re: Ctrl+wheel does not work on a fresh ini
Posted: 2024-11-07, 10:41 UTC
by ghisler(Author)
Maybe it's from MS Office?
Re: Ctrl+wheel does not work on a fresh ini
Posted: 2024-11-12, 15:48 UTC
by ghisler(Author)
Any other suggestions for a better default font than Verdana? Microsoft Sans Serif seems a bit too narrow for reading larger texts.
Otherwise I will move this thread to fixed bugs.
Re: Ctrl+wheel does not work on a fresh ini
Posted: 2024-11-13, 15:22 UTC
by MaxX
2ghisler(Author)
Well. Not so much to suggest.
Another option is Tahoma. It has been the default font for classic themes in Win 2k...7, just before ugly Segoe family came.
Tahoma has the same symbol's shape, but is not so wide as Verdana. And it has been included even in win 9X, so there should be no problem too.
Both Microsoft Sans Serif and MS Sans Serif are similar to Arial by the symbol's width. Enough pretty to print, but not so comfortable to read from displays. Here Tahoma and Verdana look better.
p.s.
Just if we talk about fonts...
I could argue about any sense of Segoe instead of Tahoma in main interface parts. But UseNewDefFont=0 helps to solve the problem for me.
Re: Ctrl+wheel does not work on a fresh ini
Posted: 2024-11-21, 10:06 UTC
by ghisler(Author)
This thread has become more a suggestion thread for other fonts, so I'm moving it to the suggestions forum.
Moderator message from: ghisler(Author) » 2024-11-21, 10:06 UTC
Moved to suggestions
Re: Ctrl+wheel does not work on a fresh ini
Posted: 2024-11-21, 11:06 UTC
by AntonyD
2
ghisler(Author)
Not only about the font:
it’s still very clear and hasn’t been sorted out point by point, this:
And what should only ONE action do - the unchecking of any checkmark from 3 available?
When it is checked and there is a label text next to it - that this is the "default" state - so all is clear here. Probably....
And looks like it's not - coz It is already becoming incomprehensible: Why is the font selection button enabled immediately
after this text??!
ALTHOUGH according to the logic of the word by "default" - button should be UN-AVAILABLE, because the built-in process of
assigning a default font is currently active... Isn't it?
Well, of course, the NAME of this “default” font chosen was implied to see right now and here - Visually to view IMMEDIATELY!
But this name is not presenting here on the dialog anywhere. Only dots-dots-dots.... You have to "dig deeper" to see it(((
Well, if we uncheck this "one" checkmark, then it seems like the font selection button should become available. ONLY now!
BUT! If we don’t do anything other than unchecking this mark, then nothing will change!! It turns out that the working with
this tick and only with it makes no sense... The only and necessary condition is to work with the font selection button?
it's about this:
https://i.ibb.co/By56WH0/bug.png
