[Digikam-devel] [Bug 139547] tag hierarchy automatic fill

[Arnd Baecker]

On Wed, 17 Jan 2007, Achim Bohnet wrote:

> On Wednesday, 17. January 2007 10:21, Arnd Baecker wrote:
> > [[ This isse was attached to
> > http://bugs.kde.org/show_bug.cgi?id=139547
> > which is Resolved now and
> > seems to have gotten lost ....]]
> >
> > On Fri, 5 Jan 2007, Daniel Bauer wrote:
> >
> > > In this regard I have a small suggestion: I'd change the order of
> > > the items in the drag and drop menu (1: assign to Selected 2: to
> > > Dropped, 3: to All), because I think usually you do an action for
> > > the selected items, only sometimes just for the dropped, and rarely
> > > for all.
> >
> > I strongly support this suggestion!
>
> I don't ;)  I don't like the menu at all.

Actually, I don't like it too much either, but did not feel
in the position to complain (I thought it was somehow/somewhere/sometime
decided and have to live with it, but at least with a better ordering
as suggested by Daniel).

> I must have been on
> crack when I suggested it in http://bugs.kde.org/show_bug.cgi?id=115153
> Sorry :(
>
> IMHO, the menu is overkill.  In my experience in KDE a drop action on a
> selection or only the drop object if the object is outside the selection.
> (see http://bugs.kde.org/show_bug.cgi?id=117403)
>
> Select all is easy:  Control-A, then drop the tag(s).  IMHO if one
> drops to an object outside the selection the selection should be
> cleared

I am not sure about this - sometimes one makes a complicated
selection and if one then misses the selected region by chance,
the selection is gone...
(wasn't there also a B.K.O about not loosing selections?)

> and ignored and the tag(s) only assigned to he drag object.

Hmm, somehow I would prefer if this is like canceling
(maybe one could one tell this the user this by a warning box,
because otherwise he thinks that his D&D did something?)

> This leaves us with only one action and cancel in RMB.
> Much easier and simplifies the workflow IMHO.

I agree with that.

Best, Arnd