FreeCommander Forum

Hello,

Here is my case : I have 3 files a, b, c.txt in their respective folders A, B, C themselves sub-folders of D:\TEMP\MULTI_SELECTED_DIR_TEST :
Searching recursively in the parent directory MULTI_SELECTED_DIR_TEST behaves as expected, showing all 3 files :
When I only select folders A and B and check "Search in selected files/folders", I would expect a.txt and b.txt to show up in the search result but as a matter of fact, none appear :
Is it a regression (I thought it uses to behave as I expected) or have I missed something about that feature ?

Thanks

K.

No problem here.
Exactly same test works fine for me.

Hi Marek,
That's extremely weird : I do encounter that behavior in whatever subdirs I select from any folder.
Of course it can include several folders in "Folders" field (little "+" icon)
But as soon as I check "Search in selected files/folders", I won't get any result (nor any log message in Log tab)
I made sure I had selected criteria neither in Timestamp (attributes all default black squared or even all selected) nor in Filters tabs (nor in Duplicates)
I now use FreeCommander XE 2021 Build 841 64-bit donor on Windows 10.0.18363.1256
(Community, ) Am I the only one to whom it occurs ?
Thanks
K.

I can't reproduce it either, tested with my custom and default setting and tree enabled, exactly as on screenshots.

FC 841 donor 64-bit, Window 10 20H2 64-bit.

Hi Dreamer,

Thanks for your efforts.

I'm stunned by those experiments

Do you agree that by selecting folders A and B from regular FC panel and searching in selected files/folders, I should get the same result as expliciting folder lists in Folders field (unchecking search in selected files/folders, right ?) :
...because that's the only thing I change between those two different results... (and now using Build 841 64-bit donor)

I'm experiencing the same error as kino,

Nothing is found when the option 'search in selected files/folders' is activated, and several folders are selected.

It works when testing with default settings.

Best regards,

FreeCommander XE 2021 Build 844 64-bit donor
Windows 10 Pro 64-bit Version 20H2 Build 19042.868

I'm still suffering from this issue in latest version.

Select a few folders and press Ctrl+F
enter search term and start search
Nothing is found.
if I deactivate 'search in selected files/folders' files are found, but then the search begins at the root folder.

As stated previously, using default settings i.e. works as it should.

How am I supposed to figure out what is causing the issue?

Thanks in advance for your help.

FreeCommander XE 2021 Build 845 64-bit donor
Windows 10 Pro 64-bit Version 20H2 Build 19042.870

I looks I can reproduce it if the option in menu - Option - "Add wildcards to file name" is disabled, when I search for "test". If that option is enabled, it works good. Not sure if it's a bug, I don't think so, if the option is disabled and I type "*test*", it works good too.

Hey Dreamer,

thanks for looking into this.
Add wildcards... was activated the whole time. It makes no difference if this is activated or not.

Just for info, I was searching for file types, i.e. .jpg and not for file names (or parts of names).

also searching for file names or parts there of doesn't work.

I will uninstall FC, clean registry delete everything under AppData\Roaming\FreeCommander

and see if it relieves the issue. This will take time, as I have to record all my settings first so I can quickly reinstate them after a new installation. I'll report back when I'm done.

Best regards,

A clean install eliminated this issue.
It was a tedious and time consuming task. I would only suggest it be used as a last resort. I spent 9+ hours getting it done.
I will post insights in another thread.

A note here, above I mentioned 'AppData\Roaming\FreeCommander'

as we all know, settings are contained in 'AppData\Local\FreeCommander' and it is necessary to delete this folder for a true clean install. Beware, backup all settings and move them to a different folder for later use (and analysis maybe).

Best regards,

Good reflex from Odamn-Ete to reinstall ! (along with a possible Windows reboot ;-> )

It has been my starting point and I felt quickly relieved by the fact that only FreeCommander.find.ini was concerned (couldn't face the idea of completely re-customizing FC !)

A couple of dichotomic tests and I nailed it :

RunAsExtProcess=0 is the default and I had set it to "Run in external process" from Options menu.

So for some reason, when RunAsExtProcess=1, multiple folders or whatever other parameter doesn't get passed correctly to the child process.

Well, not a urgent problem since it works fine within the same process but It'll be nice to have it work that way too.

Thanks

K.

Hey kino,

great job for looking further into this, you got the issue nailed!!

confirmed,
when the option to run the search UI in a separate process is active and
search in selected folders is active

NO FILES ARE FOUND

Best regards,

FreeCommander XE 2021 Build 846 64-bit donor
Windows 10 Pro 64-bit Version 20H2 Build 19042.985