[Digikam-devel] [Bug 146337] Tag regions of an image

[Fri13]

https://bugs.kde.org/show_bug.cgi?id=146337





--- Comment #14 from Fri13 <friiduh gmail com>  2010-04-28 22:14:32 ---
"For the ctrl+drag vs. drag: How about a "New area" button? At least with the
Map Search, we had some users asking how to make the selection, and thus now
display a hint if there is no selection."

That has a valid point for bringing up the feature. But it is would make
difficult to add multiple region tags for photo because between regions user
would be needed to click a button and then drag a region.

If the button would like a "On/Off" button, it would be harder again to drag
photo for panning. And what should happend when user selects other photo or
other tag etc?

There is needed somekind indicator for that. Thats why I think it would still
be best that panning would happed from middle mouse button and region selection
would happend from left drag. This way we have mouse scroll always for view
options (zoom in/out, pan, 1:1/fit). But that is the other topic for getting a
same kind functions to all around digiKam features.

We need to think how users want to tag photos. Example for me, I go trough all
photos with one tag. So that results to multiple "circles" to go trough them.
Same time I can re-rate the photo if it starts feel someway different. As far
the tagging persons has be one of the biggest jobs. So when we get it automatic
(or mostly automatic) it will cause less "circles" (at least for me).

One way what I was thinking, was if user selects/creates region tag and then
user is asked to drag a area. Like if you drag a region tag over photo, you are
informed to drag then a region.

And I came just up that it should be easy to move the region tag. So we could
just add region tags to photos and then go later just to reposition them
correctly.
Should that need a "edit" function what would lock/unlock region tag from
mistakenly happening moving?

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.