


Tagsave() //save tags now (typically to "\tag.dat") This flag is ignored if "file" is set to a DB different from the currently Note that whether database is actually read is also controlled by the value Some reason your current tags in memory do not match the status of the Can be useful in a multi-user tagging context if for If the path or file doesn't exist it will be created without askingĭefaults to the currently loaded database ().Ĩ = SafeSave: This value is only useful in Multi-User Tagging.īefore writing, the current saved state of the database is read and matched meaning of return value depends on what happened This function does not change any data on disk, just the tags in memory.Įcho tagcheck(1) //returns count of orphansĮcho tagcheck(2) //remove orphans, returns count of removed orphansĮcho tagcheck(4) //remove dupes, returns count of removed dupesĮcho tagcheck(8) //correct capitalization, returns count corrected itemsĮcho tagcheck(14, 1) //remove orphans and dupes, correct capitalization, include removables Return: Count of removed, if none count of corrected, if none count of orphans. Syntax: tagcheck(flags, )ġ = Also scan items located on removable drives.īackground: You normally don't want to throw items out of your DB justīecause a particular USB drive isn't plugged in. Fixed as well (comes with next Help update).Īction: Checks and repairs the state of the current tags. This info was also missing from the Help. Message was missing and you just encountered an error.
XYPLORER BETA PORTABLE
! Sync Folders: Sync Folders never supported portable devices, but a corresponding It's not always possible to avoid it, but % Toolbar: Smarter positioning of extra long drop-down menus so the menu doesn'tĪppear directly under the mouse pointer. + Small Lists: With no item selected, you can now use Ctrl+Up/Down to move the focus. Tags-in-memory to be attached to the new name.
XYPLORER BETA UPDATE
Hear from the rename via Auto-Refresh, but it did not automatically update the ! Multi-User Tagging: When another client renamed a tagged item, your instance would % Multi-User Tagging: Now if TagDatSafeSave=1 a superfluous DB reload after Note that TagsFlags will still work in for backward compatibility. TagsFlags=1 'bit 1 = tags DB headers are read-only TagFlags=1 'bit 1 = tags DB headers are read-only The new section just to keep everything together. * Admin Settings: The key "TagsFlags" has been renamed to "TagFlags" and been moved to Protects your Catalog from accidental dragging. + Catalog: Added another value to the tweak CatalogFlags (bit field): This will also help in fixing any fresh bugs.

It's a good idea to backup your complete XYplorer settings (menu File | Settings Special | Backup Application Data Folder.) before running a new BETA version. Note that BETA versions are work in progress and might contain fresh bugs.
XYPLORER BETA MANUAL
(1) Installer Package, (2) No-Install Package (for manual unpacking). If you prefer to download the BETA version, choose one of these packages:
XYPLORER BETA UPGRADE
To easily upgrade to this BETA version from XYplorer, hold down the CTRL key while you click Help | Online Support | Check for Updates. Modified (by someone else) since this instance last read or wrote it. The default 1 ("when necessary") means that the DB will only be read if it has been This key allows the admin to control whether "SafeSave" is used when saving your + Admin Settings: Added a new section Tags with a new key TagDatSafeSave whichĭefaults to 1 (if Admin.ini exists but the key is missing). "SafeSave" is only executed if "FileTagDat" is This latterĬondition has now been dropped. "Configuration | Information | Tags | Auto-refresh tags" was enabled. This mechanism was activated when eitherĪ shared database was defined via admin settings ("FileTagDat" key) or when To the tags in memory, and only then saved. Implemented on 20221109 where when saving tags, the database was first read, matched * Multi-User Tagging: A safety mechanism (called "SafeSave" internally) was
