Displaying fields as plain text without conversion and not fixing strict M/N numbers gives chance to load fields one needs while skipping others. Extra fields of XY are very flexible but it is difficult to guess what each user stores in those XY fields. Setting configuration via ini file will be enough. Is it possible to have a sort of «function» like read(M,N) to read XY extra field M to Everything custom property N without any conversion ? Those who prefer rating stars could use readstar(M,N).
Relative + absolute paths is good enough for me. I see no useful scenarios with that storage=2 option. The Storage parameter is a little difficult to support as Everything doesn't know where the portable XYplorer application is located.Įverything will currently always treat the paths as relative to the tags.dat file location.
#Xyplorer manual pdf full
Line 27: Tagged item #1: Full filename|LabelID|Tags|Extra1|Extra2|Extra3|Extra4|Extra5|Extra6|Įxtra7|Extra8|Extra9|Extra10|Extra11|Extra12|Extra13|Extra14|Extra15|Extra16|Comment Line 7-22: Extra Tag Definitions: Caption|TypeID|0|0|||||. Line 1: Header and version info: XYplorer File Tags v5 The file is kept in an open, simple, and human-friendly text format (UTF-16 Text File) so that youĬan easily edit it manually using an editor or programmatically using any scriptable software.įile Format of the XYplorer Tag Database (version 5 - from 19.70 onwards) All tag data are retained across sessions and stored in one file, tag.dat, located in the application dataįolder.
0 kommentar(er)
