Columns Viewer

Buttons/Scripts
, ,
45

Hi.
Since the scripts I’ve created—and some I’ve shared here—have received several internal updates that haven’t been published, I’ve decided it’s better to release them periodically rather than keep them to myself, letting them gather dust and fade into oblivion.
So, starting with this script, version 2.0a, introduces a lot of changes:

  • Speed! Significant performance improvements.
  • New Data Retrieval Method: A faster and more efficient approach without using temporary files.
  • Progress Bar: Now included within the dialog itself.
  • Internal Command Overhaul: Now uses two parallel tasks, contributing to the speed boost.
  • Now has support for even more built-in columns!
  • Improved Search Methods: Enhanced and more flexible search capabilities. Instant search is also improved.
  • Wildcard Support: Expanded to support Opus wildcard syntax.
  • Advanced Search Mode: A new, powerful way to refine results (see syntax below).
  • New Arguments: Now you can choose which columns to display!
    • INCLUDE: Include only the listed groups/columns (supports wildcards).
    • EXCLUDE: Exclude the listed groups/columns (supports wildcards).
    • Additional Switches: REGEX/S, CASE/S, WHOLEWORDS/S, DIACRITICS/S, WILDCARDS/S, ADVSEARCH/S.
  • Support for most of the columns in 'This PC', so you can actually use it in that context if you want to.
  • Some options in Script Config are no longer valid : values obtention method and dialog size mode.

Notes and some Technical Stuff:

  • Password-protected archives might prompt for a password, which is beyond the script’s scope to handle.
  • INCLUDE and EXCLUDE Arguments:
    • Values are separated by commas (e.g., mp3*,*count*).
    • To refer a "group" you can use grp: followed by the column's type (audio,pictures,script,etc).
    • These type of arguments (Keyword type) are treated and passed as single strings by Opus. So if a value includes spaces or commas, it might break the parsing (currently I'm just using split(',') :sweat_smile:). So, that might be another clue that using a comma or space in the actual keyword of a script/evaluator column is not a good idea.
      Advanced Search Syntax: Support the following syntax:
    • $n|l|h|v|t(==|!=)"value" ; where:
      • $n: Name
      • $l: Label
      • $h: Header
      • $v: Value
      • $t: Type (group)
    • Example: $t=="audio" AND $v != "" ; to list all the audio columns whose value is not empty.
    • In this mode, instant search is disabled, requiring you to press Enter to perform the filtering.

Important:

Since some features (like INCLUDE/EXCLUDE for customizing data) have been added very recently, there may be bugs. Please report any issues you encounter if you decide to test this command.

ColumnsViewer.opusscriptinstall (22.8 KB)

4 Likes