Philippe
Philippe
@wpferguson we may need you help here. This is an old issue. The tags on the path of a leaf tag (reference to the tree view) are part of the...
A bit of context to explain why we need the above. Two years ago with the tag `places|AT|Wien` attached to an image we had the following choices for exporting: -...
> If I understand correctly the goal is to export the tags AT and Wein, without also exporting places? No, export tags already works like that. The goal here is...
> What does making AT a tag provide us that we don't already have? If the only goal is to make the tag AT export in a certain case, then...
If we agree on the goal, it is time to discuss about what we do. @quovadit, what's your idea ? As @wpferguson said, we don't want that other users complain...
I would not take the risk. At least a lua preference could help to keep everyone satisfied. Then, coded as you have done in tags.c [# 8270](https://github.com/darktable-org/darktable/pull/8270/files), you access the...
> I already removed the db-access after review We may not talk about the same one. I'm talking about dt_lua_tag_get_reference_count() -> dt_tag_count_tags_images() which calls the db. Here is my suggestion:...
> If it will be a C function, wouldn't it be obvious to move the whole lua-script to darktable core? (preferences in tagging module) That's a valid question. It would...
Not a bug. Like this since 2015.
At the beginning it was a gear wheel button next to the export one. I moved it to the module's preferences when working on other modules' preferences. There is no...