After some further examination of the problem, I have opened a pull request to have the change reversed [1] <https://github.com/darktable-org/darktable/pull/1662>.
-- August Schwerdfeger aug...@schwerdfeger.name On Mon, Mar 12, 2018 at 11:28 PM, August Schwerdfeger < aug...@schwerdfeger.name> wrote: > Is there any way to replicate the former behavior (collecting by the exact > tag) without doing a two-rule "tag 'Tag' but not tag 'Tag|%'" query? (I am > currently wanting to do some collections of images that have some child tag > but not the parent tag, which is, I think, impossible to replicate with the > two-rule setup.) > > -- > August Schwerdfeger > aug...@schwerdfeger.name > > On Mon, Mar 12, 2018 at 12:21 PM, Tobias Ellinghaus <m...@houz.org> wrote: > >> Am Sonntag, 11. März 2018, 03:48:24 CET schrieb August Schwerdfeger: >> > With Darktable 2.2.5 and earlier, when collecting by tag, if one typed >> in >> > the name of a tag (e.g., 'Parent') it collected only the images with >> that >> > exact tag. >> > >> > With Darktable 2.4.0, this behavior changed so that typing in the name >> of a >> > tag also collects images with any of the tag's descendants in the >> hierarchy >> > (e.g., 'Parent|Child'. >> > >> > Was this intentional? >> >> Most likely, yes. >> >> > -- >> > August Schwerdfeger >> > aug...@schwerdfeger.name >> > >> > ____________________________________________________________ >> _______________ >> > darktable developer mailing list >> > to unsubscribe send a mail to darktable-dev+unsubscribe@list >> s.darktable.org >> >> > ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
