It would be nice to get some information when content plugin fields are used but the associated plugin isn't installed. Currently nothing is displayed where the field values are expected. This can be a custom plugin view. As the user cannot see if the field is really empty or the plugin is not installed this lead to strange assumptions. So in this case a hint should be placed inplace of the field value.
Another case is a loaded 'saved search'. Here conditions defined on the plugins tab are simply removed when the plugin isn't installed but if the user never controls all tab contents there is no way to see which conditions have been used in the search. In this case I would expect a warning when loading the search
Make unavailable plugin fields more visible when used
Moderators: white, Hacker, petermad, Stefan2
Support+++
License #524 (1994)
Danish Total Commander Translator
TC 11.03 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1371a
TC 3.50 on Android 6 & 13
Try: TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
Danish Total Commander Translator
TC 11.03 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1371a
TC 3.50 on Android 6 & 13
Try: TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
- ghisler(Author)
- Site Admin
- Posts: 48166
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
What would you suggest? What about numeric fields?
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
I don't think that there can be a good general result for missing field contents.ghisler(Author) wrote:What would you suggest? What about numeric fields?
What about an error message showing the missing field reference,
with the options to continue (behaves as its now) or aborting.
Windows 11 Home x64 Version 23H2 (OS Build 22631.3593)
TC 11.03 x64 / x86
Everything 1.5.0.1376a (x64), Everything Toolbar 1.3.3, Listary Pro 6.3.0.78
QAP 11.6.3.3 x64
TC 11.03 x64 / x86
Everything 1.5.0.1376a (x64), Everything Toolbar 1.3.3, Listary Pro 6.3.0.78
QAP 11.6.3.3 x64
I always find prefixed exclamation marks quite useful in such cases, as they are rarely used in plug-in values.
So for custom columns you would see sth. like:
in all requested fields.
But I agree: there is probably no overall solution for all possible places where wdx plug-ins are used. So a short messagebox with the error message might be best, though it's probably best to make it optional through an ini option.
So for custom columns you would see sth. like:
Code: Select all
(!)
But I agree: there is probably no overall solution for all possible places where wdx plug-ins are used. So a short messagebox with the error message might be best, though it's probably best to make it optional through an ini option.
TC plugins: PCREsearch and RegXtract
I don't really understand why the field type matters in case the plugin is not installed. I would have expected that TC checks if the plugin is installed before allocating memory for the field results. Or why does it matters?What about numeric fields?
For the custom column view and similar something like this:What would you suggest?
http://lefteous.totalcmd.net/tc/ideas/missing_plugin_v1.png (this is the Unicode placeholder character which is used when a character is missing in a font.
http://lefteous.totalcmd.net/tc/ideas/missing_plugin_v2.png (a more chatty approach)
For loaded searches a simple warning message box would be sufficient.