Cannot scroll text in Lister when FTP is waiting

[Slavic]

This is a kind of weird bug: to reproduce it, you have to find an extremely slow FTP server.

Imagine: after successful FTP connection you command TC to enter some directory and are waiting for result (and try to make something useful in the same time). All the time until server's response the scrolling in Lister is being completely disabled. No difference, was the Lister opened before FTP connection of after it (e.g. if you wish to see the FTP log). After response the scrolling restores as usual.

[petermad]

Confirmed - but only when using the scroll wheel.

If I use the scroll bar, Lister scrolls alright.

If I use the arrow keys, Lister scrolls about 10 lines, pauses for a short while and then scrolls about 10 lines - and so forth.

[Slavic]

Of course, I have scrolled using a mouse wheel and decided that it's obvious, sorry

[ghisler(Author)]

This is the same problem as described by other users with lister and a busy Total Commander: When TC is waiting for something in a local message loop, then many functions in lister cannot work. The only workaround is to use the external Lister from www.ghisler.com/addons.htm instead of the built-in Lister.

[Slavic]

Well, Christian, I check this workaround with external Lister and it really solves the problem with scrolling external documents. Or, as I understood, a general problem with dispatching messages when TC is in busy state. However, two catches are currently left, which I has to mention about.

1. The publicly available version of Lister is outdated in compare to built-in Lister in TC 7.0. In particular, that Lister cannot show the HTML in UTF-8 encoding without tags, as new Lister can. Could you make available the standalone Lister 7.0 in current beta state?

2. The FTP history is always shown in built-in Lister, even the external Lister has been set as default. So, the problem with scrolling the log of slow FTP server cannot be solved now.

P.S. The standalone Lister saves its configuration in the WINCMD.INI file in %windir%, regardless to ini file location, which has been set for TC.

[ghisler(Author)]

1. I will make available the new lister when TC 7 is finished. It's just too risky to publish a beta version now.

[dumbledore954]

I will make available the new lister when TC 7 is finished. It's just too risky to publish a beta version now.

Hello Mr. Ghisler,

something visible at the horizon?

[ghisler(Author)]

It has been available here for a while already:
https://plugins.ghisler.com/beta/lister32.zip

Unfortunately I got very little feedback, so it's still in the beta section.

[karlchen]

It has been available here for a while already:
https://plugins.ghisler.com/beta/lister32.zip
Unfortunately I got very little feedback, so it's still in the beta section.

Oh, I see:
lister.exe 495.040 04.07.2007 09:38 -a--
Hm, I did not even realize that there was a newer version than the one I had: lister.exe 487.936 12.06.2007 12:14 -a--
Telling from the readme, the only difference seems to be the added MANIFEST for XP and Vista.

As I use the external lister only for viewing 1 particular (large) logfile 99% of the time, I cannot really give too much feedback, except that it works fine for viewing text files. Have not configured any multimedia plugins to be used by the external lister. They are all handled by the internal lister.

Regards,
Karl

[DoubleT]

Unfortunately I got very little feedback, so it's still in the beta section.

I tried this version, but have some trouble with redirected sections in wincmd.ini.

lister.txt
/I=ini_file name Set different name of INI file, default is wincmd.ini

wincmd.ini
Viewer=%COMMANDER_PATH%\lister.exe

[Lister]
RedirectSection=%COMMANDER_PATH%\tools.ini

[ListerPlugins]
RedirectSection=%COMMANDER_PATH%\plugins.ini

[ghisler(Author)]

Lister.exe does not use redirect section options.

[petermad]

Lister.exe does not use redirect section options

What a shame

[DoubleT]

Lister.exe does not use redirect section options.

And why the readme (lister.txt) points out to the wincmd.ini as default, if it doesn't support it?