Bulk apply/remove a tag on a set of activities?

[pnlshd]

Hello again

I wanted to ask if there is a way to bulk apply (add) an activity tag to a set of activities or also remove a tag from them (if they have it) instead of doing it one by one from the UI.

[Liviu Lalescu]

Hello again, pnlshd!

No, unfortunately there isn't. I will add your suggestion in the TODO.

[pnlshd]

Thank you, Liviu

There was also another suggestion to consider if you like and it is a quite simple one, when I regenerate a timetable using multithreading I always get the prompt to first rename the folder, I suggest that this message become a Yes/No prompt to overwrite rather than an info message to enforce renaming from me.

[Liviu Lalescu]

You are welcome!

I also added this suggestion, but:

1) It is very risky for me/FET to remove the old multi results directory (the whole current file directory must be removed completely before the new generation).

2) The whole point of disallowing multiple generation overwriting is to make sure the hard earned results are not removed with a single click. You might press Yes and easy like that the possible precious results are gone.

[pnlshd]

That is true and I understand why you enforce that, maybe you can add a third option "rename" so "yes" will overwrite but rename will create a new folder with an incrementing numeric suffix. It could also be just No and Rename if you like too to prevent accidental overwrite.

[Liviu Lalescu]

OK, I will add also these words, and think of the problem.

[pnlshd]

Thank you for your consideration, Liviu. All the best for you and for FET 🥳

[Liviu Lalescu]

You are welcome! Thank you!

[Liviu Lalescu]

Hello, pnlshd,

I thought about it. A good idea might be to write each time the new timetables in another directory, if the current one exists. So, first it saves in liviu-single, then in liviu-single-2, then in 3, ..., 9, 10, for single generations, and similarly with liviu-multi.

The only drawback is that the disk space usage might grow much if the user does not notice that the old results are kept.

@Volker Dirr , what do you think?

[Volker Dirr]

I think the idea is good.
Don't forget that the user should see the directory name (in the GUI and also in fet-cl mode.)

About disk space:
In TiTiTo I read the backup folder and warn if there are too many files.
Maybe we can do it similar in fet. Just counting the number of directories in the fet-results folder and if there are too many, then warn. (Of course we could also count the file size, I just suggested counting the directories, since it is faster)

[Liviu Lalescu]

Thanks, Volker!

I have in mind only GUI change. The FET-CL can change the output directory in the command line options.

Hmm... about too many directories: I prefer not, because it does not exactly reflect the size. The user will see them. But if you strongly suggest, I will try to do this.

[pnlshd]

Hello,

Thank you for thinking about this!

I agree that the count of directories does not reflect size.

and yeah it is a good idea to check of a directory exists and then increment the last numeric suffix.

could also add this as an option to enable or disable in the settings by default.

[Liviu Lalescu]

I did it. I made a snapshot announcement in the Snapshots section. The link, directly:

https://lalescu.ro/liviu/fet/download/test/

I don't add any kind of warning or setting. I hope the users will manage. I just increase the numbers and add new directories.

Please let me know what you think.

[pnlshd]

I tried it and it works perfectly in single and multi, good job 🥳

[Liviu Lalescu]

Thank you! I only worry about users' disk space...