https://bugs.kde.org/show_bug.cgi?id=461206
--- Comment #3 from Tobias Leupold <t...@stonemx.de> --- Well, this approach would also work, as whilst reading the database, we have to read through all tags anyway, and thus can identify the untagged images tag. Anyway, to keep the current functionality, a "meta='untagged'" structure is not sufficient, as the user can choose whether the tag should be visible or not. Either, we extend this (e.g. store some JSON key-value data inside that meta property or such), or we remove the setting and decide that the untagged images tag should always be hidden. If we always hide the untagged images tag, the benefit would be we can simply generate any name (e.g. an UUID or such) for it and don't have to mess too much with possible collisions. -- You are receiving this mail because: You are watching all bug changes.
