Ctrl+wheel does not work on a fresh ini

[AntonyD]

Use fresh INI - open with Lister any massive text file and try to ZOOM it.
You will fail. Now go to FONTs settings box Insides 'Configure Lister' dialog
and uncheck 'ANSI' default checkmark. And choose `Lucida Console` for ex.
NOW the ZOOMing process will work.

P.S.
And what should only ONE action do - the unchecking of this checkmark?
When it is check IN and there is a label 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 the further button for selecting fonts is AVAILABLE?!
ALTHOUGH according to the logic of the word by "default" - it should be UNAVAILABLE, because the built-in in a code of
assigning a certain default font works. Well, of course, the NAME of this “default” font was implied to see right now and here
Visually visible IMMEDIATELY! But this name is not presenting here on the dialog anywhere. You have to "dig deeper" to see it...

Well, if we uncheck this 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 working with
this tick and only with it makes no sense... The only and necessary condition is to work with the font selection button?

[ghisler(Author)]

Not a bug, fixed fonts can't be zoomed because there aren't enough available sizes. See also
viewtopic.php?t=84187

[AntonyD]

Do you accurately answer the question, entering the situation from the position of a Total user?
Globally Stated support for this action. I was told somewhere + I didn’t read tons of references
preliminary, all that they told me was how easy and fast it works for my friend.
And so I came home, installed this new version, opened the file, held down CTRL,
turned the mouse wheel and..... and nothing happens.
Are you sure that in such a situation I will go to help, here to the forum and try to find out
the reason for this? Or will I just say to myself, that this is another bug that simply no one
has fixed?

If the problem is in the initially assigned fonts, then it is necessary to find and offer the most
suitable ones by default. It seems that current the "default" fonts are only for opening in Win9x.

And you also did not comment on the essence of my thoughts in P.S.

[ghisler(Author)]

As I wrote in a different thread, I couldn't find any good looking fonts with fixed character widths which would be available on all systems. I can't just include a font either, for copyright reasons. One solution would be to use a different font depending on the Windows version, but that would also cause problems with the portable version. any other ideas?

[MaxX]

2AntonyD
Not a problem here.

2ghisler(Author)
I think it would be enough to make a description in help that user can use zoom option for custom selected TTFs.
And may be add some short text string for page of font customization about this too. Some thing like that: "Use custom font (TTF type) to make font zooming feature available" (or something better to understand than this one).

[AntonyD]

Not a problem here.

You could not reproduce this bug? ON a fresh INI?

I couldn't find any good looking fonts with fixed character widths

but why we stopped in searching in that subset of very non-userfriendly fonts?
why not TTF?

[MaxX]

why not TTF?

Tell us any of monospaced TTF fonts with DOS and Windows char sets. Just any.

[AntonyD]

Why do we look for monospace TTF fonts?
for better code viewing? IMHO for this definitely any non-regular user will have his famous fonts collections.
I thought that we are here talking about ANY simple text viewer capabilities available right out-of-the-box.
And for this, only two conditions are enough - they support UNICODE and scale well.

[MaxX]

2AntonyD
DOS (ASCII) and Win (ANSI) are not about unicode at all.
Looks like you don't even understand the usage of monospaced fonts.

[AntonyD]

And this can happen. But then try to tell it in a more understandable format than what can be found on the wiki or somewhere else.
AND please pay attention that in my words in the first post I paid attention ONLY to the first checkbox (although my thoughts in P.S.
should be considered in relation to all three). So in our communication now we should only care about the "ANSI" encoding. Or if to be
more precisely, all those encodings that begin with CP... After all, the ANSI term, as we well know, is a misnomer because these Windows
code pages(CP) do not comply with any ANSI (American National Standards Institute) standard.

[petermad]

I think the problem for AntonyD is that if for exampe Lucida Console is chosen as font for ANSI, and that is saved, then if you open the configuration dialog again and click the "default" box, then the button still shows Lucida console - it is not until you have closed the configuration dialog and opened it again that the button is blanked.

[AntonyD]

2petermad
Yes - and that includes this! Thank you for clarifying! I somehow forgot to describe this moment in detail.
BUT this is just an addition to what I described! Not just my situation described differently by yours words!

[Usher]

As I wrote in a different thread, I couldn't find any good looking fonts with fixed character widths which would be available on all systems.
(...) any other ideas?

What about using DejaVu Sans Mono font? It's available on SourceForge site
For DOS it should work when using option "ASCII/DOS (local code page (1)" from "Encoding" menu rather than pressing "S" hotkey.

FixedSys Excelsior is almost identical as system Fixedsys, but it's a duospaced font (f.e. it has wide letters in Russian/Ukrainian).

[ghisler(Author)]

I found out that on NT based systems, all fonts work as OEM when setting the font family to OEM.
Therefore I will now use the font "Consolas" (size 11) as the default for both ANSI/Windows and ASCII/OEM when the font is present, otherwise I will keep using the FIXEDSYS and Terminal fonts. "Consolas" is the same font as used by notepad, which should make it easier for users to adapt to it.

As for variable, I would suggest Arial, what do you think? any better ideas?

[MaxX]

Verdana should be more comfortable to read than narrow Arial due to lot of reasons.