Hi void.
I wonder if there's any chance of including custom field values from files, but kind of like how Everything currently handles .metadata.efu files — meaning one file per folder instead of one giant monolithic csv.
FWIW, I don't care if Explorer can see these values, I just want Opus (which already works) and Everything to be able to.
Custom fields in sidecar files but per folder
Re: Custom fields in sidecar files but per folder
I'm not quite sure what you want.
Everything already has .metadata.efu files.
custom property 0-9 can be used for custom values.
You can define any column names you like.
but if Everything doesn't know the property from the column name, the value is ignored.
There's also support for user property values with User values.
But this is just a giant monolithic csv file.
Everything already has .metadata.efu files.
custom property 0-9 can be used for custom values.
You can define any column names you like.
but if Everything doesn't know the property from the column name, the value is ignored.
There's also support for user property values with User values.
But this is just a giant monolithic csv file.
Re: Custom fields in sidecar files but per folder
Thanks void, and sorry for not being clear.
From the info about .metadata.efu here, I had the impression it only supported columns that Explorer also supports, and not custom user ones, but it seems that's not the case, right?
And my question was also about whether there's maybe some kind of support for additional .efu files (or others types) besides .metadata.efu, with the goal of keeping custom column values separate from other metadata (making it easier to possibly manage that data).
About custom_properties_0-9, can you tell Everything the data type of a column? Or how does it tell the difference between a numeric value and a date, for example?
From the info about .metadata.efu here, I had the impression it only supported columns that Explorer also supports, and not custom user ones, but it seems that's not the case, right?
And my question was also about whether there's maybe some kind of support for additional .efu files (or others types) besides .metadata.efu, with the goal of keeping custom column values separate from other metadata (making it easier to possibly manage that data).
About custom_properties_0-9, can you tell Everything the data type of a column? Or how does it tell the difference between a numeric value and a date, for example?
Re: Custom fields in sidecar files but per folder
Only the Filename column must exist.From the info about .metadata.efu here, I had the impression it only supported columns that Explorer also supports, and not custom user ones, but it seems that's not the case, right?
You can have any other columns you like.
Everything will understand Everything properties and Windows Property System Properties.
Everything will ignore anything else.
Strictly .metadata.efu only at this stage.And my question was also about whether there's maybe some kind of support for additional .efu files (or others types) besides .metadata.efu, with the goal of keeping custom column values separate from other metadata (making it easier to possibly manage that data).
Maybe in the future this could be extended to .tag.metadata.efu for just tag properties, but it would require some configuration..
custom_properties_0-9 are string values only.About custom_properties_0-9, can you tell Everything the data type of a column? Or how does it tell the difference between a numeric value and a date, for example?
custom numerical values might be added in a future version of Everything.