Search also in Windows Properties

[Check Master]

Hello everyone,

I've added a column representing the Windows property 'Description'.
I know that I can search in 'only' that specific column by RMB on the column header and select 'Search for Description'.

Question:
Is it possible to search always also in that property column?
In other words, is there an option or setting to include such a column in the standard search results?

I already add the property to the index and looked at the help which says 'Adding a property to your index will: • Make searching for this property instant.'
I've tried to recreate the database but noticed no difference.
Is there different behavior for 'Windows properties' or 'Everything properties'?

Anyone?

[therube]

Tools | Options | Indexes -> Properties --> Add...

will bring up a Select Properties dialog, where you can then select, Description,
which will then add Description into your database.

[void]

Is it possible to search always also in that property column?
In other words, is there an option or setting to include such a column in the standard search results?

Please consider the following filter:

• From the Search menu, click Add to filters....
• Change the Name to: Filename or Description
• Change the Search to:
  
  #replaceterms:#(:$param:#):,#(:<#term:|description:#term:>#):
• Click OK.

Filters can be activated from the Search menu, Filter bar (View -> Filters), right clicking the status bar, filter macro or filter keyboard shortcut.
Filters can be organized from Search menu -> Organize filters.

I already add the property to the index and looked at the help which says 'Adding a property to your index will: • Make searching for this property instant.'

Everything will take some time to index the Description property for your files.
Progress is shown in the status bar on the right.
The search will be instant.
However, it will only match files that have been indexed.

Is there different behavior for 'Windows properties' or 'Everything properties'?

They are essentially the same.
Everything will use the Windows property system first, then has some built-in fallbacks.

[Check Master]

Thanks both for your reaction.
@therube
I already tried.

@void
I've added the filter as described and make it the active filter.
It looks like it didn't work here.

For my understanding:
You write:
Everything will take some time to index the Description property for your files.
Progress is shown in the status bar on the right.
The search will be instant.
However, it will only match files that have been indexed.
My index is complete, so a filter should not be necessary when the search is instant?
Still I won't see the result when searching.

Maybe this information helps:
• When I do a 'RMB search' on the Description column I see strange behavior which I'm not used to from Everything.
• I've recorded a video which makes it visible, for this video I've narrowed down the indexing to that specific folder, see this link:
https://drive.google.com/file/d/1pYQvO9 ... sp=sharing

Thanks in advance for your help.
Greetings.

[void]

I suspect you are indexing the Windows Property System Description property and searching the Everything Description property.

This will be really slow.

Please make sure you are indexing the Everything Description property:

• In Everything 1.5, from the Tools menu, click Options.
• Click the Properties tab on the left.
• Double click Description.
• Select the Everything Description property and click OK.
• Click OK.

Does the issue persist?

[Check Master]

@void

The 'search thing' I have tackled by replacing 'description' with 'property-system:solidworks.document.description'.

Glad that this is working.

The 'instant search' is still not working,while the property is indexed, or so it seems.
Any help is very appreciated.
Thanks in advance.

[Check Master]

Our messages crossed.
Thanks for the support.

Can you help me with the 'instant' search?
Am I reading this correctly, based on indexing of this property it should be 'Everything fast'?

[void]

The search should be instant.

Did you update your filter search to:

#replaceterms:#(:$param:#):,#(:<#term:|property-system:solidworks.document.description:#term:>#):

Could you please send your Help -> Troubleshooting information.

[Check Master]

Thanks for your answer 'The search should be instant', I'm curious towards the solution.

Yes, I did update the filter accordingly, when I activate the 'File Name & Description' filter it is working fine, but not with the 'Everything Fast' speed.

Please find the 'Troubleshooting Information':

Code: Select all

Everything:	1.5.0.1383a (x64)
OS:	Windows NT 10.0 19045 (x64)
Admin:	0
Service:	1 (connected / installed and running)
Command line:	-path "S:\Wipers\Marine\Decca\Decca New Concept\Decca SLW Test Frame Equipment"
Binary:	C:\Program Files\Everything 1.5a\Everything64.exe
Profile:	C:\Users\...\AppData\Roaming\Everything\Everything-1.5a.ini
Database:	C:\Users\...\AppData\Local\Everything\Everything-1.5a.db
Instance:	1.5a
Config:	match_whole_filename_when_using_wildcards=0
Config:	filter=EVERYTHING
Config:	preview_visible=1
Config:	columns=[{"name":"Name","width":535},{"name":"property-system:Solidworks.Document.Description","width":318},{"name":"Path","width":769},{"name":"Size","width":67},{"name":"Date Modified","width":99},{"name":"Date Created","width":99},{"name":"Type","width":133}]
Config:	ntfs_volumes=[{"path":"C:","volume_name":"\\\\?\\Volume{...97}"}]
Config:	folders=[{"path":"G:"},{"path":"S:"}]
Config:	properties=[{"name":"property-system:Solidworks.Document.Description","include_only_files":"*.sldprt;*.SLDPRT;*.sldasm;*.SLDASM"}]

[Check Master]

In my last post regarding 'Troubleshooting Information':
'Fast Sort' was not active for the 'Description' property (property-system:solidworks.document.description).
I turned it on and re-scan the index, but no difference for 'Instant Search'.
I have tried before too to change that setting to see the difference, searching for a solution.

Code: Select all

Everything:	1.5.0.1383a (x64)
OS:	Windows NT 10.0 19045 (x64)
Admin:	0
Service:	1 (connected / installed and running)
Command line:	-path "S:\Wipers\Marine\Decca\Decca New Concept\Decca SLW Test Frame Equipment"
Binary:	C:\Program Files\Everything 1.5a\Everything64.exe
Profile:	C:\Users\...\AppData\Roaming\Everything\Everything-1.5a.ini
Database:	C:\Users\...\AppData\Local\Everything\Everything-1.5a.db
Instance:	1.5a
Config:	match_whole_filename_when_using_wildcards=0
Config:	filter=EVERYTHING
Config:	preview_visible=1
Config:	columns=[{"name":"Name","width":535},{"name":"property-system:Solidworks.Document.Description","width":318},{"name":"Path","width":769},{"name":"Size","width":67},{"name":"Date Modified","width":99},{"name":"Date Created","width":99},{"name":"Type","width":133}]
Config:	ntfs_volumes=[{"path":"C:","volume_name":"\\\\?\\Volume{...97}"}]
Config:	folders=[{"path":"G:"},{"path":"S:"}]
Config:	properties=[{"name":"property-system:Solidworks.Document.Description","include_folders":1,"include_only_files":"*.sldprt;*.SLDPRT;*.sldasm;*.SLDASM","fast_sort":1}]

[void]

Thank you for the logs.

After some testing my end there's a performance hit when searching indexed Windows Property System properties and using this filter.

This slowness is caused by many API calls to render text.
Currently, Everything will make API calls to render text for empty values.
This is slow and unnecessary.
The next alpha update will no longer attempt to render text for empty values and text.
Your search will be instant.
I will have an update soon.



What other Solidworks properties are shown in Everything under the Windows Property System?
I will look into merging these into the Everything properties.

[Check Master]

Hello, thanks again for your reaction and explanation, I will eagerly look forward to the update.
It would be great to be able to use this.

What other Solidworks properties are shown in Everything under the Windows Property System?
I will look into merging these into the Everything properties.
A: For now I only use the 'Description' Solidworks property.

What I would like to clarify for my understanding: After the update, do we need the filter or should it be enough to have the properties indexed?
Am I correct when I say: Indexing has no effect now, it is the filter that does its job and takes a lot of time?

[void]

I'll make a post here once I have something for testing.

What other Solidworks properties are shown in Everything under the Windows Property System?
I will look into merging these into the Everything properties.
A: For now I only use the 'Description' Solidworks property.

I mean, what are all the available Solidworks properties listed in Everything under Windows Property System?
I would love to map all the Solidworks properties to the existing Everything properties, so you can just index the Everything Description property.
(Everything properties are much faster than Windows Property System properties as there's no translation of values and no API calls to convert to text)

What are the common Solidworks file extensions?

What I would like to clarify for my understanding: After the update, do we need the filter or should it be enough to have the properties indexed?

You will need the filter.
Consider a short alias to search the Solidworks Description property:
For example:
In Everything, from the Search menu, click Add to filters...
Change the Name to: Solidworks Description
Change the Search to:

property-system:Solidworks.Document.Description:$param:

Change the Macro to:

sd

Click OK.

Change your active filter to: Everything
Now when you search for

sd:"my description"

your search is replaced with:

property-system:Solidworks.Document.Description:"my description"

Am I correct when I say: Indexing has no effect now, it is the filter that does its job and takes a lot of time?

Property indexing will make searching faster.
The filter will search your filenames and your Solidwork descriptions as normally only the filename is searched.
Everything will force you to specify property-system:Solidworks.Document.Description: to search that property.
Without property indexing, a

property-system:Solidworks.Document.Description:

search would be extremely slow.

[Check Master]

Thanks again for this detailed explanation.
That clears up a lot for me.

Searching with 'sd:"my description"' does not work with multiple search terms, is that correct?
While '#replaceterms:#(:$param:#):,#(:<#term:|description:#term:>#):' does that job.

About all available Solidworks properties, see picture:

2024-11-20_124018.png (33.23 KiB) Viewed 1165 times

[void]

Searching with 'sd:"my description"' does not work with multiple search terms, is that correct?

Use subexpressions with your sd: macro.

For example:

sd:<"My description 1"|"My description 2"|"My description 3">

sd:<blue sky>

Alternatively, use multiple sd: calls:

sd:"My description 1" | sd:"My description 2" | sd:"My description 3"

sd:blue sd:sky

Thank you for the solidworks property list.
Sorry for not knowing these.
I see the same list with my Solidworks 2019 install..

The next update (1384a+) will map the following Solidworks properties to Everything properties:

Windows Property System Property	Everything Property
Solidworks.Document.Description	Description
Solidworks.Document.Author	Author
Solidworks.Document.LastSavedWith	Software

These mappings will only occur for the following file extensions:

.sldasm
.slddrw
.sldprt

Please let me know if I am missing any extensions.

[Check Master]

Thanks for your explanation again, very nice to be taken along in the workings of the program.
I am not a programmer but I am not unfamiliar with it, I have done something with code and from that point of view I admire enormously what you are doing and you are creating a beautiful piece of software.
Isn't it time to donate? Certainly, just did


Sorry I missed answering your question about Solidworks file extensions, the ones you mention are correct.


Thanks for pointing out subexpressions and 'multiple calls'.
However, that is not nearly as easy as the 'normal Everything way of searching' that I experience with the 'Filename or Description' filter.
For example, there the order of the search terms does not affect the results, see picture with some result:

[void]

Thank you for your donation and support Check Master,

Thanks for pointing out subexpressions and 'multiple calls'.
However, that is not nearly as easy as the 'normal Everything way of searching' that I experience with the 'Filename or Description' filter.
For example, there the order of the search terms does not affect the results, see picture with some result:

The | will break out of your sd: search and search filenames.

The next update (1384+) will support sd:cyl;nut

; = OR

For now you will need to use

sd:cyl | sd:nut

[void]

Everything 1.5.0.1384a adds support for sd:cyl;nut

Everything 1.5.0.1384a improves searching Windows Property System properties.
Empty values are no longer rendered.
Text values are no longer rendered.

[Check Master]

Can I ask you a programming question?
In Everything, when you choose 'Open Path', an already opened File Explorer is taken. In my case with QtTabBar installed, it gives a new tab, exactly what I want.
How do you get it to take the existing File Explorer.
When I try that in VB NET, I keep getting a new File Explorer and I can't figure it out.

Greetings!

[void]

Everything calls SHOpenFolderAndSelectItems

[Check Master]

Wow, thank you so much.