Make Lister and QuickView title bars fully configurable

[Gral]

Similar to main TC window title, please add an option for change, with new ini entries (default if missing or empty) e.g.:
ListerTitleBar=Lister - [<filepathname>]
QuickViewTitleBat=<filename> - <pluginname>
or
TitleBarLister=
TitleBarQuickView=

[petermad]

Support++

[Horst.Epp]

Support++

[jinsight]

Support++

[ZTom]

Support++

Can you give us a short feedback on the status of your decision whether this feature will be implemented on near future or not?

Thanks!

[Fla$her]

I'm against it because Lister and Quick View have the same class, so only "Lister " at the title beginning allows them to be programmatically distinguished when searching and identifying a window (example).

[Gral]

Please stop asking not to add options to TC, just because you don't need it personally.

NRN

[Fla$her]

Please stop asking not to add options to TC, just because you don't need it personally.

Before duplicating other people's words from another topic, take the trouble first to at least catch the resulting difference. Programmatic universal identification is a necessity that will be broken by implementing this suggestion, while the options suggested in that topic will not negatively affect anything like this.
There is a big difference between 'I don't need it' and 'this will harm'.

[monarch-lfv]

Similar to main TC window title, please add an option for change, with new ini entries (default if missing or empty) e.g.:
ListerTitleBar=Lister - [<filepathname>]
QuickViewTitleBat=<filename> - <pluginname>
or
TitleBarLister=
TitleBarQuickView=

++Support

Since it will be customizable, the Fla$her's anxiety can be configured in a way that is convenient for him.

[JOUBE]

Support++

[Fla$her]

Since it will be customizable, the Fla$her's anxiety can be configured in a way that is convenient for him.

I advise you to read carefully what I wrote. Simply put, one thing should not interfere with another in case an insufficiently competent user, who has previously used someone else's (reference) code, wants to make the proposed setting, not realizing that already used ones that are no less important will break.

[white]

Moderator message from: white » 2026-06-14, 09:38 UTC

Please refrain from personal attacks. Be nice to each other and keep comments focused on the topic.
(This is addressed to all people.)

The forum rules and guidelines can be found here.

[monarch-lfv]

2Fla$her
What exactly will break? After all, the proposed option can be customised exactly as it is now, so that nothing changes in terms of automation. You will also distinguish the Lister window from the Quick View window by the word "Lister" in the title.

[Fla$her]

2monarch-lfv
I wrote that it will break — programmatic universal identification. This is not a private or individual issue. This is a matter of code functionality for everyone who uses it.

Code: Select all

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

This setting, however absurd it may seem, cannot be allowed a priori.

It's roughly the same as suggesting an option to change the class of some window, which could previously be used by others for identification. An explanation like "you can change the class in the old code or not use the new option" doesn't apply to all users, especially those who are not well-versed in this but use ready-made solutions. ghisler(Author) is even afraid to break new buttons and settings for users, let alone the old ones.

[Gral]

Did you write to AutoHotKey (and similar tools) author(s) with request to remove this harmful posibility allowing change any window title?