>>5485
I expect to extend the siblings/parents system so parents apply to all siblings.
I will make sure this applies retroactively, so that existing siblings get the parents of any of their other siblings along the chain.
i.e. if you have:
siblings A->B and B->C
and
parent B->P
After the update, all A and C will get P.
Once this works, you can 'rename' a tag while maintaining relationships by just adding a new sibling.
If you literally want to rename a tag but keep all the counts and everything exact, then if you are brave you can edit the db file directly. Make a backup of client.master.db in your db directory and then run sqlite3.
Do something like this:
.open client.master.db
UPDATE subtags SET subtag="better_tag" WHERE subtag="bad_tag";
.exit
Or you can browse the db more sensibly in a proper application like SQLiteStudio.
Messing around with this stuff may obviously cause problems if you either mess around or affect tags on your cache of the PTR (the PTR will not think the tags are called that, if your client ever talks to it about them).
>>5495
The siblings and parents dialogs are a huge mess behind the scenes. The more relationships that get added, the less well they work. It all needs an overhaul, and I expect to make a portable HydrusTagArchive kind of way of storing and importing/exporting siblings and parents. At this point, it should be much easier to allow easy import/export!