[KPhotoAlbum] Associating multiple tags with one area?

Df458 hugues.ross at gmail.com
Sun Oct 5 20:28:40 CEST 2014


> If someone would implement this, one would
> have to think about how to handle multiple tags. A list of all tags would
have
> to be created and the user would have to be able to maintain it in a
> convenient way, without a drawback for the "single tag" users.
Ok, I actually have an idea about this so let me run it by you guys
before I try it: Currently(at least in the version I'm using),
there are two menus.
First:
Associate with <some tag>
Associate with [menu of tags]
Remove Area

Second:
Remove tag <some tag>
Remove Area

My proposal would theoretically make a menu like this:
Associate with <some tag>
Associate with [menu of tags]  --This would add a tag on top of what's
there.
Remove tag [menu of tags] --This would show added tags
Remove all --This lets single-tag users keep removing with 1 click, and
benefits multi-tag users
Remove Area

If you think this would work, I can probably implement it myself.

> What do you do with the areas so that you need more than one tag?
It might seem a bit silly, but I like getting extremely specific with
tagging. I tend to add a lot of arbitrary data about the people who are
tagged, so being able to define which subject these tags relate to would
be helpful for sorting through stuff later. I realize it's a pretty rare
use-case, but I'm sure I can't be the only one out there who does this.

On Sun, Oct 5, 2014 at 1:17 PM, Tobias Leupold <tobias.leupold at web.de>
wrote:

> Hi Hugues(?),
>
> > Is there any simple way to add multiple tags to one area?
> No, this is currently not possible. One tag per area.
>
> > If not, is there anything serious preventing this feature from being
> > implemented?
> Well, probably, one could implement this somehow. But the intention behind
> the
> positionable tags was to be able to tag faces (on current git master, we
> already have face detection and face recognition). Tagging faces, we don't
> need multiple tags per area but only one. With this in mind, we did the
> implementation.
>
> The way the data is stored in the database is the following:
>
>         <option name="People">
>                 <value value="Someone" area="1713 817 164 164"/>
>         </option>
>
> so probably, other tags could "simply" reference the same area and thus be
> added as tags to the same area. If someone would implement this, one would
> have to think about how to handle multiple tags. A list of all tags would
> have
> to be created and the user would have to be able to maintain it in a
> convenient way, without a drawback for the "single tag" users.
>
> (Without elaborating this idea completely) I think this is anything but
> trivial to do ...
>
> What do you do with the areas so that you need more than one tag?
>
> Tobias
> _______________________________________________
> KPhotoAlbum mailing list
> KPhotoAlbum at mail.kdab.com
> https://mail.kdab.com/mailman/listinfo/kphotoalbum
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kdab.com/pipermail/kphotoalbum/attachments/20141005/5822efd5/attachment.html>


More information about the KPhotoAlbum mailing list