I often use a content plugin (especially xpdfsearch) to rename files in multi rename tool. The problem is that I often don't know which field is the right (or best) one - because I have to insert the field first, it's a bit trial and error.
So my idea would be to add some kind of preview to the file selection. This would be the value for the first file in the list. What do you think?
Preview content plugin values
Moderators: Hacker, petermad, Stefan2, white
Preview for selected field could be added to content field selection window if it would be realized. E.g. focused file could be used for it.
I support the idea in general, but I think you have to take care with delayed/on demand fields (ft_delayed and ft_ondemand).
For those you probably need some additional configuration, to let the user choose if he really wants to preview the field in focus,
cause a preview is probably expected to load in an instant, and taking several seconds for it might be confusing to the average user.
for which, even with a disk cached file, it would take some time to retrieve all fields, and, like above, delayed/on demand fields might take ages for a result.
IF we get a WDX plug-in interface update some day, I'd vote for a new field flag,
sth. like e.g. "fast_duty", where the author assures that this particular field will only load minimal data from the file (low disk I/O) and parsing won't take long,
and therefore such field might be shown as preview in any case.
For those you probably need some additional configuration, to let the user choose if he really wants to preview the field in focus,
cause a preview is probably expected to load in an instant, and taking several seconds for it might be confusing to the average user.
I'd say it pinpoints a similar problem as above: a preview will take time, for once because some plug-ins have tons of fields,MVV wrote:Preview for selected field could be added to content field selection window if it would be realized. E.g. focused file could be used for it.
for which, even with a disk cached file, it would take some time to retrieve all fields, and, like above, delayed/on demand fields might take ages for a result.
IF we get a WDX plug-in interface update some day, I'd vote for a new field flag,
sth. like e.g. "fast_duty", where the author assures that this particular field will only load minimal data from the file (low disk I/O) and parsing won't take long,
and therefore such field might be shown as preview in any case.
TC plugins: PCREsearch and RegXtract
- ghisler(Author)
- Site Admin
- Posts: 50873
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
This feature has been added to the upcoming TC9 in April 2015.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
Great! I'm looking forward to the first beta.ghisler(Author) wrote:This feature has been added to the upcoming TC9 in April 2015.
And I'm curious how the slow fields behave with that feature.
TC plugins: PCREsearch and RegXtract
- ghisler(Author)
- Site Admin
- Posts: 50873
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
I'm using the "delay if slow" option, so they should show a default string.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com