Multiple Tag Lists?

[n2tpa]

In the Help file, I found this statement: "You can also manually manage the Tag List in List Management. This way you can easily load a new cloud to have a different set of tags ready for selection."

I have a couple of different volumes with very different usage and would love to be able to use two totally separate tag lists when tagging & searching these two volumes.

How do I accomplish this? I searched the forums and didn't find anything directly related to this, and the roadmap doesn't address it either.

N2TPA

[admin]

Check for the scripting command taglist().

NB: I just was shocked to see that it is missing in the index of the Scrpting Commands Reference...

[n2tpa]

I have the "Home" version....no scripting. Should I assume this feature is only available by using scripting?

[admin]

I have the "Home" version....no scripting. Should I assume this feature is only available by using scripting?

Oh.

[n2tpa]

Admin,

If you're inclined to add it to the Home version, I certainly won't stop you.

If it's too tough to do, then I suppose I could embed a separate XYPlorer program group within each volume. That way, each would have its own "XYPlorer.ini" and "Tags.dat" files. I would then simply have to open the correct one to have the desired label and tag list.

Your choice.

N2TPA

[admin]

The tag list is stored in XYplorer.ini (not in tag.dat). You can load different INI files on startup via command line switch.

[n2tpa]

Admin,


You 'da man!

...or put another way, Thank You very much for an elegant and simple solution.

N2TPA

[TheQwerty]

I have the "Home" version....no scripting. Should I assume this feature is only available by using scripting?

Seems like a good time to mention that XYplorer Pro is currently (but only for the next 17 hours) half-off on BitsDuJour.

You may want to consider upgrading.

[n2tpa]

Qwerty,

I was poised to smugly respond with all the reasons why I chose the version I did. Instead, I sat and thought about it for a couple of minutes:

"If I upgrade now, it will cost me about $2 more than if I'd bought the Pro version initially."
"If I don't take this deal, the upgrade will cost me considerably more later..."
"If there's one Undocumented feature that needs a Pro license, there may be others I'll find in the future".

In other words, you talked me into it. I ordered the Pro version as soon as I got home from work. It was a simple process that took all of 5 minutes.

Now, being a scripting virgin, how do I implement the tag-list change using scripts?

N2TPA

[admin]

Try this in the "On click" field of a user button:

Code: Select all

"tag list 1" taglist("jan,feb,march");
"tag list 2" taglist("may,june,july");
"tag list 3" taglist("oct,nov,dec");

And check Fire click on mousedown. That way you have a dropdown menu of tag lists for easy switching.

[TheQwerty]

I was poised to smugly respond with all the reasons why I chose the version I did.

Sorry if I came off as criticizing your decision to purchase the Home edition - that wasn't my intention. Just wanted to point out that there was a deal going on in case you were considering the upgrade.
Again, sorry!

[n2tpa]

Guys,

First to ADMIN: Thanks for the guidance. It works beautifully. I appreciate the quick response.

Then to QWERTY: I didn't take it as criticism in the least. In fact, with your gentle prodding I was led to a well though-out decision. Thank You.

One more question to both of you: On the Home Edition, to make my installation truly portable between my work machine and my home machine, I needed to change the drive letters contained in "XYPlorer.ini", and "Tags.dat". The volume stays the same between the machines; only the drive letter changes.
With the addition of scripting and the catalog, etc, what other files will remember root drive letters that will need to be changed?

N2TPA

[admin]

One more question to both of you: On the Home Edition, to make my installation truly portable between my work machine and my home machine, I needed to change the drive letters contained in "XYPlorer.ini", and "Tags.dat". The volume stays the same between the machines; only the drive letter changes.
With the addition of scripting and the catalog, etc, what other files will remember root drive letters that will need to be changed?

Right, "portable paths" are not implemented everywhere. For example tag.dat could be made portable in that way (at a performance cost at startup, depending on the number of tags). BUT: Then it would not be processable anymore by other software (because it is unlikely that other software understands XY's portable path syntax). I like to think the open format of tag.dat has some value. (Although I have to admit I never got any feedback on this.)