[Digikam-devel] [Bug 167571] New: Unnatural order when removing images from light table

[Andi Clemens]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=167571         
           Summary: Unnatural order when removing images from light table
           Product: digikam
           Version: unspecified
          Platform: Compiled Sources
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: NOR
         Component: Light Table
        AssignedTo: digikam-devel kde org
        ReportedBy: andi.clemens gmx net


Version:           0.9.5-svn / 0.10-svn (using KDE 3.5.9)
Installed from:    Compiled From Sources
Compiler:          gcc-4.3.1 Linux (i686) release 2.6.25-ARCH
OS:                Linux

When you remove images from the light table, the order of removing them is a little bit unnatural, at least for me.

Right now removal behaves like this (codes: L = left pane, R = right pane, 1-5 image in thumbbar, * = current):

1. removal of last image:
    L1 2 3 4 R*5 => L1 R*2 3 4

2. removal of left pane image (the right pane is always assigned to the left pane)
    1 L*2 3 R4 5 => 1 L*4 R3 5

3. removal of left pane if last in thumbbar
    1 2 R3 4 L*5 => 1 2 L*3 R4

For me it feels much more natural if removing images from the thumbbar works like this:

1. removal of last image (right pane):
    L1 2 3 4 R*5 => L1 R2 3 R*4

2. removal of left pane image:
    First try to select next image to current left
    1 L*2 3 R4 5 => 1 L*3 R4 5
    
    If next is current_right, select prev.
    1 L*2 R3 4 5 => L*1 R3 4 5
    1 2 R3 4 L*5 => 1 2 R3 L*4
    
    If no next or if prev is current_right, select first image in thumbbar
    1 2 3 R4 L*5 => L*1 2 3 R4

    if no prev and next is current_right, "move" pair
    L*1 R2 3 4 5 => L*2 R3 4 5

This way the current_left and current_right pane image stay as long as possible where they are and will not be switched all the time like it is now. I'll provide a patch for this behavior. Please test it. What do you think? For me it just "feels" right in terms of usability.

Andi