[Feature Request] Excluding Images based on path

[youyinnn]

Hi, a feature like excluding settings is great.

Scenario:

Suppose I have two folders for images:

1. folder a: contain 1,000,000 images; which I am not interested in;
2. folder b: contain 100 images; which I want to observe all the time;

In this case, loading 1,000,000 is too much, and the image viewer stops responding.

[smithereensarr]

确实急需排除功能，安装了.fvm以后，现在打开插件，就会很卡。.fvm里的文件都会被检索出来，非常让人困扰。

[ZhangJian1713]

@youyinnn @wangweiarr The function of the exclude path has been completed, and I hope to get feedback on the use experience from you.

[RichardWepner]

I was roughly testing the directory exclusion and it seems to work as I would expect it: paths are excluded relative to the project directory.

However, which paths to exclude depends on the type of project. In a Unity project, Unity creates a Library directory and stores files - including the package cache, and packages in Unity frequently also contain images - in there to easily find the right data. Since this directory also includes images that are picked up by the extension, they are shown if the project directory is used to preview the project images. This is typically undesirable, since these images include documentation images and can't be managed (removed or renamed). An Unreal project might have other paths that typically want to be excluded, etc.

Since the settings don't seem to be stored per project (I didn't check it, though), it might be good to add some configuration to exclude paths per project using the VSCode settings. From my perspective, either relative paths as they are used already, or paths including VSCode variables could be used, for simplicity while editing I would rather suggest relative paths.

I think it would be enough if this setting is only accessible through the VSCode preferences (or file editor), since showing them in the UI would only work if an additional input for them is offered, and I don't know if VSCode even offers to adjust the settings from extension views.

A Nice to Have feature would be a button to open the preferences editor for this setting directly, however I don't see this as necessary.

[ZhangJian1713]

Since the settings don't seem to be stored per project (I didn't check it, though)

Each project has its own independent local configuration file, For macOS, this directory is ~/.vscode/extensions/vscode-infra.image-viewer-1.6.1/projectsConfig/***.json

A Nice to Have feature would be a button to open the preferences editor for this setting directly

I'm not sure if you have tried this button and pop-up.

[Klaster1]

The current exclusion mechanism check matches against complete path. Matching the path against a regex or glob would help immensely in cases where path are dynamic (test screenshots in my case).