Filter by Column : Powerful filtering/searching tool for all columns

I took the following two pictures in English language

2024-04-08_132700

Update v1.5.9 Beta 1 :

GENERAL:

  • Dialogs should now use the font name and size configured in Preferences / Colors and Fonts / Fonts > Dialogs.
  • Now is possible to show matches for nested items (either from an expanded folder or when grouped flatview is on) from within a library.
    • Note than show matches for nested items is only available when not using Textual Filters (when enable_wilcards==false and preferred_filter_mode==1)
    • Not available when using Multi Mode.
  • Changed command's label (because it was too large)

FAYT:

  • Multi mode can now be used via FAYT mode (by enabling the Multi Mode flag)

DIALOG:

  • Changes to 'Refresh' button in the dialog. Now always shows all items in the tab and synchronizes them with the dialog (before it was a bit confusing about which items to show and which not).
  • Checked values are remembered under certain circumstances (e.g. when changing/editing a category).
  • Columns that have the same header are now suffixed with their keyword (so overlapping columns are avoided and ALL built-in columns should be listed now)
  • All Labels (including non-explicit ones) are now listed.
  • Fixed filtering issues with nested items.
  • The dialog now is able to avoid continous call for the same tab.

For those who are actually using this on a daily basis, please try this new version and report if anything isn't working as it should.
(@David @JCDARK @evernessince you may want to update as well)

4 Likes

Very nice update!

v1.6.0 (Apr 13, 2024) : FilterbyColumn.opusscriptinstall (needs at least v13.4.8)

  • GENERAL:

    • Dialogs will now use the font style and size you've set up in Preferences / Colors and Fonts / Fonts > Dialogs.
    • Now you can see matches for nested items within a library, whether it's in an expanded folder or in grouped flat view.
    • Changed the command label because it was too long.
  • FAYT/COMMAND:

    • Textual Filters now support showing matches for nested items. To enable this, set nested results with Textual Filters to true.
      • Just a heads-up, this might slow down the operation significantly. (workaround is not good enough but it works :slightly_smiling_face:)
    • Multi mode is now accessible via FAYT mode by turning on the Multi Mode flag.
    • In Multi Mode, if only one column is used, it switches back to the regular procedure, which can be faster in some cases.
    • Added a busy indicator during filtering, allowing you to cancel the operation if it's taking too long.
    • New arguments in COMMAND mode : CONFIG and EDITCATEGORIES.
  • DIALOG:

    • Script columns can now be listed during initialization.
      • This includes automatic recognition of the data type, providing general benefits. For example, you won't need to register the column type if the dialog has been initialized at least once, unless you want to change the registered type.
    • Added new entries in Script Configurations: list Script Columns, list Evaluator Columns, and list Shell Columns, to toggle the listing of these columns during dialog initialization. (Useful if you have a large number of columns of a certain type, as listing them all could slightly delay the display of the dialog.)
    • Changes made to the 'Refresh' button in the dialog. It now always displays all items in the tab and syncs them with the dialog (previously, it was a bit confusing regarding which items to show).
    • Checked values are now remembered under certain circumstances (e.g., when changing/editing a category).
    • Columns with the same header are now suffixed with their keyword, preventing overlap and allowing all supported columns to be listed.
    • All item labels, even non-explicit ones, are now listed.
    • Fixed filtering issues with nested items.
    • The dialog now avoids continuous calls for the same tab.
    • Fixed some issues with edited categories been replaced when listing custom columns.

Now that the command can successfully list basically columns of all types, including script columns, and recognize the data type of each column, it's easier to use directly without needing to pre-register the type in the script configuration. If you want to change any column type that hasn't been previously registered in custom_columns_categories, you can do so via FilterByColumn EDITCATEGORIES or by using the pencil icon in the DIALOG. You can disable the listing too, if you have many custom cols, which may cause the dialogue to take longer to appear, from settings.

2 Likes

:warning: IMPORTANT: Needs at least Directory Opus v13.5.1
v1.6.1 (Apr 21, 2024) :

  • Fixed some empty values not allowing to unhide items in DIALOG mode.
  • Improvements when selecting items in DIALOG mode.
  • Code updated/cleaned up.
  • Better logging system.
1 Like

How do you select a column?

How to apply several conditions for a filter by a single column? For instance I want to search 14d and 2-5m in date column.

How do you select a column?

Just click on the column header.

It makes the column to change the order (ascending/descending), not selecting it like on the footage.

Yes, but in order to set the focus for filtering by column, it is required. If you don't want to change the order, you can click the column twice, and have it set for the filter script.

Not only it didn't work (first column was being filtered despite clicking on date), but also the column didn't get highlighted (selected) as on the clip.

Hold Ctrl and right-click a column header (to select the whole column) or cell (to select individual cells).

The script uses that selection for its own purposes, but you can also right-click it to copy the selected data to the clipboard.

Finally a real solution! This selects and highlights the column exactly like on the video. Thank you.

No idea why people are trying to propose a help when they don't know

@errante

Filter by '%1'.dcf using v1.6.1 : FilterbyColumn.opusscriptinstall with Opus 13.5.5 crashes in all tests. Ideas?

The most likely thing is that you placed it outside the column headers menu. :grinning:

Assuming you're talking about this button, which is working here right now.

Now, if you're referring to a 'crash' within the script itself, feel free to message me and include the script log, along with additional context regarding the specific error. I'll take a look when I have some free time

I used the button you sent me and ran it by right clicking on the column header.

Script Log Output.txt (2.7 KB)

Thanks

That log has no relation to this command. :slightly_smiling_face:
Also, I believe those kinds of errors should be reported to Leo or Jon (in another post).