Actualising a filter change

[chrisjj]

Is there a single command that updates the Only Compare Files (sic*) display to reflect a change in Filters:? Currently I use Edit | Expand All, then Edit | Collapse All.

Thanks.

* I think this label should be Compare Only Files - a different meaning and the one that accords with program behaviour.

[Tim]

Changing name filters should take effect immediately. There seems to be a bug that prevents the file counts in the statusbar to be updated if you happen to be positioned on a folder when the filter changes. Is this what you are referring to?

[chrisjj]

No. I change the filter to e.g. *.GIF such that folders containing no *.GIF will be hidden.

[Aaron]

Hello Chris,

In the Folder Compare, under the View menu, there are 4 options:
Always Show Folders
Compare Files and Folder Structure
Compare Files only
Ignore Folder structure.

Are you using the Compare Files only option? This option will hide folders if all the files inside are filtered out, or the folder is empty. Edit: This option behaves like BC2.

[chrisjj]

> In the Folder Compare, under the View menu, there are 4 options:
> Always Show Folders
> Compare Files and Folder Structure
> Compare Files only

"Only Compare Files" here.

> Are you using the Compare Files only option?

As I said in the root, I am using "Only Compare Files".

> This option will hide folders if all the files inside are filtered out

That is what I am trying to get the refresh to do.

[Aaron]

Could you post or email a screenshot to [email protected] ?

With that folder option set to Only Compare Files, and all items inside the folder are filtered out, the folder itself should disappear if it is not aligned to a folder that is still present.

[chrisjj]

>Could you post or email a screenshot

Will two do?

1 Set Filters: to *.wav
2 See:

3 Expand, Collapse
4 See:


> With that folder option set to Only Compare Files, and all items inside the
> folder are filtered out, the folder itself should disappear ...

In this case it does so only upon Expand, Collapse.

[Aaron]

Thanks for the screenshots. The Yellow color implies they are not scanned yet, and are not scheduled to be scanned due to the current Session Settings (otherwise, if they were scheduled they would be White/Transparant). Expanding or Double clicking them is triggering a manual scan.

Try going to the Session Settings, Handling, and enable "Scan top level Orphan folders" as well as "Automatically scan subfolders in the background". Does that work for you?

[chrisjj]

> Expanding or Double clicking them is triggering a manual scan.

Yup. And I'm asking if there is a one-click trigger.

> Try going to the Session Settings, Handling, and enable "Scan top level
> Orphan folders" as well as "Automatically scan subfolders in the background".

I have

[X] Automatically scan subfolders in background
. .[ ]Automatically scan top-level orphan subfolders

Why is that proving insufficient?

[Aaron]

>
I have

[X] Automatically scan subfolders in background
. .[ ]Automatically scan top-level orphan subfolders

Why is that proving insufficient?

Because the yellow folders in your screenshots are Orphans at the top level. The default Session settings for Beyond Compare do not open and scan Orphan folders since there is nothing to compare against. You can easily change this default behavior if you want it to scan them to by checking to Automatically scan and selecting Also Update Session Defaults.

[chrisjj]

> Because the yellow folders in your screenshots are Orphans at the top level.

They meet the criterion "Automatically scan subfolders in background" so should be scanned. Suggestion: make label and behaviour accord.

Meanwhile, could you answer the original question? Thanks.

[Aaron]

Chrisjj,

I did answer the question. I'll try to rephrase. Top-level Orphan folders (the yellow ones in your screenshot) are not expanded or compared by default. Since there is nothing on the other side, we do not scan them since the scan is potentially a large task and the folder is an Orphan regardless. An example could be they are very large tree structures on an FTP and performing the LIST command could be expensive.

This is the default behavior. We include the sub-option to expand the Orphan folders if you want to. Set this option, then set it as the default if you want to have this option enabled for all future sessions as well. With the option enabled, we will expand and scan the top level Orphan folders, apply file filters, etc. With the other option we set earlier (Only Compare Files), the scanned folders will be hidden from view if there are no visible files inside.

This combination should meet your original post's requirements. If it does not, please include a screenshot or specific example you are having trouble with.

[chrisjj]

> I did answer the question.

No. The question is:

>~> Is there a single command that updates the Only
>~> Compare Files (sic*) display to reflect a change in Filters:?

and you gave me an interesting and detailed explanation of the default behavour and options.... which does not answer the question.

> This combination should meet your original post's requirements.
> If it does not, please include a screenshot or specific example
> you are having trouble with.

I already did, but here it is again:



FAOD, my question is:

Is there a single command that updates the Only Compare Files (sic*) display to reflect a change in Filters:?

Yes or No will do fine.

Thanks.

[Aaron]

Yes, any change to filters will take place immediately on your comparison.

If you configure Beyond Compare to include Top-Level Orphans automatically as part of the comparison, then it will affect them as well.

[chrisjj]

>> Is there a single command that updates the Only Compare Files (sic*)
>> display to reflect a change in Filters:?

> Yes

OK, so what is the single command?

> any change to filters will take place immediately on your comparison.

As I have said, it does not.