New "File Tags" feature

[j_c_hallgren]

So no 'Lemon Chiffon" pie stains on a 'Oldlace' tablecloth, but instead 'Plum' "Tomato' stains & 'PeachPuff' w/'MintCream' crumbs?

Where do they get some of those more unusual names?

[serendipity]

Code: Select all

+ File Tags: For developers and hardcore users there's a new undocumented and unsupported SC edittags. It works directly on the memory (not on tag.dat), and it works well... :)

::edittags; from AB brings up the window, what is the syntax for direct tagging or commenting?

[admin]

Code: Select all

+ File Tags: For developers and hardcore users there's a new undocumented and unsupported SC edittags. It works directly on the memory (not on tag.dat), and it works well... :)

::edittags; from AB brings up the window, what is the syntax for direct tagging or commenting?

File|TagID|Comment

[jacky]

Code: Select all

+ File Tags: For developers and hardcore users there's a new undocumented and unsupported SC edittags. It works directly on the memory (not on tag.dat), and it works well... :)

::edittags; from AB brings up the window, what is the syntax for direct tagging or commenting?

File|TagID|Comment

Just to be clear though, this is just for fun, but it's tags/comments still aren't yet supported in scripting. What I mean is, this just brings up that window for manual editing, but it's not a way for a script to set tags/comments... right?

[serendipity]

Code: Select all

+ File Tags: For developers and hardcore users there's a new undocumented and unsupported SC edittags. It works directly on the memory (not on tag.dat), and it works well... :)

::edittags; from AB brings up the window, what is the syntax for direct tagging or commenting?

File|TagID|Comment

Yes, i know that previous tag.dat editing syntax. But I thought it would work without opening the Tag& comments window. When I tried this from AB:
edittags <curitem>|3|XY;
I thought it will add the <curitem> to the end of list and tag it, but instead it opened a window which I have to manually edit anyway. Am I doing something wrong?
Good thing though is it tags on the fly.
Update: I saw your previous post. All clear now.

[admin]

edittags: I used it for debugging stuff, and I thought it might be useful for some of you. It's not a way to tag stuff via scripting.

[j_c_hallgren]

re V7.90.80:

1) still shows "Violet" on my sys vs "purple"
2) Tag Check up would probably be better as "Clean up" as that is what it does, since check-up is more of an integrity thing in my usage

[admin]

re V7.90.80:

1) still shows "Violet" on my sys vs "purple"
2) Tag Check up would probably be better as "Clean up" as that is what it does, since check-up is more of an integrity thing in my usage

1) Violet is now part of your user settings. You get purple when you reset to defaults
2) It first checks and then cleans if necessary. Is "Clean Up" the better term for this?

[admin]

re V7.90.80:

1) still shows "Violet" on my sys vs "purple"
2) Tag Check up would probably be better as "Clean up" as that is what it does, since check-up is more of an integrity thing in my usage

1) Violet is now part of your user settings. You get purple when you reset to defaults
2) It first checks and then cleans if necessary. Is "Clean Up" the better term for this?

Looks like "Database Clean Up" is the standard term for this.

[j_c_hallgren]

2) It first checks and then cleans if necessary. Is "Clean Up" the better term for this?

Given that your dialog says

Remove any orphaned tags and comments?

...the tag database may contain items that don't exist anymore.
Click OK to remove any such items from the database now.

which only talks about removal, which is clean-up IMO, I think it's the more approp term as you have found.

BTW, on another related topic: Could the tag & comments be added to the std file info tips? In addition to having their own tooltips?

Because on my display, I barely have room for the tag col, and comments are off the screen on right, so having them avail via tips would be helpful I think, for me and possibly others.

[admin]

Because on my display, I barely have room for the tag col, and comments are off the screen on right, so having them avail via tips would be helpful I think, for me and possibly others.

Hmm, weren't you one of the DP advocators?

[serendipity]

re V7.90.80:

1) still shows "Violet" on my sys vs "purple"
2) Tag Check up would probably be better as "Clean up" as that is what it does, since check-up is more of an integrity thing in my usage

1) Violet is now part of your user settings. You get purple when you reset to defaults
2) It first checks and then cleans if necessary. Is "Clean Up" the better term for this?

Looks like "Database Clean Up" is the standard term for this.

I would like such a thing for other databases too, something I asked for once upon a time.
But I see a drawback as XY is a portable app and there might be many dead paths from several PCs which might be usable later. Hmmm tricky situation.
Could there be a way to separate paths from current PC that are truly dead (because of rename, move etc) to paths on other PCs which look dead now but are actually alive.

[j_c_hallgren]

But I see a drawback as XY is a portable app and there might be many dead paths from several PCs which might be usable later. Hmmm tricky situation.

Just a thought...could the 'bad' results optionally be dumped into a dialog similar to List Mgmt so that user could review them and decide what to do with them? Of course, maybe some sort of "Exclude list" applied to this clean up might also help.

Because on my display, I barely have room for the tag col, and comments are off the screen on right, so having them avail via tips would be helpful I think, for me and possibly others.

Hmm, weren't you one of the DP advocators?

Yes, and when we get DP, that issue may affect even more users! Now...when I use DP on x2, I reduce the cols shown to just the bare min I need for that task, and I'd expect to have to do same on XY.

[admin]

But I see a drawback as XY is a portable app and there might be many dead paths from several PCs which might be usable later. Hmmm tricky situation.

I think tag.dat is not to be ported. You have one fixed at each of your machines.

Later I will add scripting support similar to MiniTree. E.g. a command

Code: Select all

LoadTags(tagfile, [add], [colorstoo]]

Could there be a way to separate paths from current PC that are truly dead (because of rename, move etc) to paths on other PCs which look dead now but are actually alive.

I don't see a way.

[jjk]

Could there be a way to separate paths from current PC that are truly dead (because of rename, move etc) to paths on other PCs which look dead now but are actually alive.

I don't see a way.

Perhaps by List Management, by hand ? provided that we can delete several lines in one shot.