Make Lister and QuickView title bars fully configurable

[Fla$her]

What for? Third-party automation tools can change someone else's title only if there is a window, while a GUI program, when creating an interface, already uses certain constants, which are used to identify it. One does not interfere with the other. But even if it did, it would only be before the window/panel is redrawn, after which the titles return to their original appearance, unless we take cases of message flooding, of course.

[monarch-lfv]

2Fla$her
You can set it like this:

Code: Select all

ListerTitle=Lister - ...
QuickViewTitle=QuickView - ...

I understand you're concerned about users who use your ready-made automation (autorun, AHK, etc.) and don't care about the consequences of changing the title. If so, then for them, you should leave the default suggested values ​​in the INI file (as they are now), and add comments in scripts that depend on the title to remind them that the script won't work correctly if these keys are changed.
Personally, I use Lister very often in my work, and sometimes I have 20 such windows open. Because of this, instead of reasonable names of open files, I see this in my taskbar:

Code: Select all

Lister(...|Lister(...|Lister(...|Lister(...|Lister(...|Lister(...|Lister(...|Lister(...

And I have to click through them all to find the one I need.

[Fla$her]

You can set it like this:

You're walking in circles. My example concerns exclusively the impermissibility of having such a possibility.

and add comments in scripts that depend on the title to remind them that the script won't work correctly if these keys are changed.

This is not much different from the warning in the TC history about the need for all users to correct their button/command codes, etc., because some parameter or variable began to return a different value. I would even say that in your case it is much worse, because if everyone can immediately read the history when updating, then correcting the plugin's help material may happen many months after the TC release. The user will simply have nowhere to look to find out about the changes. Moreover, there is a 99% chance that he will not even see this comment and will simply perceive the problem as a new bug.

Regardless of all this, my words "one thing should not interfere with another" remain relevant. The most I would agree to is to make the beginning "Lister - " an immutable part for a separate window and massively auto-delete it for QV, if it was specified somewhere, but I doubt that Christian will do something like that.

Personally, I use Lister very often in my work, and sometimes I have 20 such windows open. Because of this, instead of reasonable names of open files, I see this in my taskbar:

To prevent the taskbar from being overcrowded with Lister windows, people have long been using tlister.

[monarch-lfv]

2Fla$her
I know the Tlister plugin, but I find it inconvenient. I generally don't like grouping programs using tabs. I prefer to have everything individually visible on the taskbar at all times.

"one thing should not interfere with another"

I agree, but no one here is suggesting breaking something that's already working. This is initially a request for a flexible change; nothing will change for you, since by default, the key values ​​in the INI will completely replicate the current functionality and header display.

[hi5]

2monarch-lfv do you use ahk yourself? If so, you could write a small script that watches for new lister windows and automatically update the title to your preference - that might be a solution until (if and when) your suggestion is implemented.

[Fla$her]

2monarch-lfv

I know the Tlister plugin, but I find it inconvenient. I generally don't like grouping programs using tabs. I prefer to have everything individually visible on the taskbar at all times.

I take the opposite view: tabs are more useful than the taskbar, because you can switch directly between them using the keyboard, rather than between all tasks in a row.

nothing will change for you

Hmmm. It was like I was wasting my time explaining. Read it again. I can't explain it any clearer. I can only repeat:

This is not a private or individual issue. This is a matter of code functionality for everyone who uses it.

[monarch-lfv]

2hi5
Yes, I'm using ahk. Thank you for the good idea, why I didn't guess myself. Moreover, I have already done this - I wrote a script, it works perfectly. But for the future, I would still like to see this functionality built into Total Commander. I hope Christian will pay attention to this topic.

2Fla$her

I take the opposite view: tabs are more useful than the taskbar, because you can switch directly between them using the keyboard, rather than between all tasks in a row.

You can't arrange tabs in a single window across two monitors for visual document comparison (not the kind of documents that can be compared using Beyond Compare and similar software).

Hmmm. It was like I was wasting my time explaining. Read it again. I can't explain it any clearer. I can only repeat:

Hmmm. And it's hard to argue with you. Especially since you seem a bit aggressive. Relax.

[Fla$her]

2monarch-lfv

You can't arrange tabs in a single window across two monitors for visual document comparison (not the kind of documents that can be compared using Beyond Compare and similar software).

One monitor is enough for me to work in TC. But you also can't arrange TC tabs on two monitors, it doesn't force you to use Explorer windows or two and or more TC instances.

And it's hard to argue with you. Especially since you seem a bit aggressive. Relax.

After all the explanations above, attempts to appeal to the individuality of the problem look like a mockery. So I've reacted calmly so far. I don't feel like banging my head against the wall anymore. I've explained everything clearly several times, but it's like you're repeating the same thesis like a mantra, which can't help but annoy.

[JOUBE]

This is a very useful extension and should be implemented as suggested by the OP.