1. That's tour, not whatsnew. They have different level of detail.j_c_hallgren wrote:Don't want to argue with you but must point out a couple of things:admin wrote:1. No, this is not the place for such details.j_c_hallgren wrote:Suggest that on http://www.xyplorer.com/release_7.90.htm#0100, the location of where the tags are stored be documented,Huh? So why then...On http://www.xyplorer.com/tour/index.php?page=catalog, I see this: "All catalog data are saved in a small file called catalog.dat and is ready for take-away." and on http://www.xyplorer.com/tour/index.php?page=cks, I see this: "The shortcuts are saved in a small binary file called ks.dat that you can travel with. "...so why shouldn't tag.dat get the same treatment?
Those are just two examples from XY site of what I meant...
Ok...so I didn't quite say it fully correctly either but I was referring to a couple of cases, such as move, where a "non-tag does NOT overwrite old tag: old tag stays", so while the tag status of the overwitten item is retained, the status of the replacing item is lost, ok?admin wrote:2. No, they are retained in all cases.j_c_hallgren wrote:Also, it implies that tags are retained with file operations in all cases, but this isn't the case when destination exists, right?
And while you do't explicitly say "Copy" in the "with file operations (e.g. move or rename).", it can be inferred via the "e.g" that it does include that, and since copy doesn't retain tags (right?), then this is in conflict with the 'retained in all cases'....adding a "as logically appropriate" could maybe be enough.
2. They are retained on Copy as well. They are just no new tags added to the DB to auto-tag the targets of the copy operation.
XYplorer Beta Club
