[digikam] [Bug 464966] Pressing Escape in Trash clears the view

2023-01-28 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=464966

Maik Qualmann  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/grap
   ||hics/digikam/commit/6ab745a
   ||426ebdcc182ca8bbb2f77cf13c1
   ||55c068
   Version Fixed In||7.10.0
 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Maik Qualmann  ---
Git commit 6ab745a426ebdcc182ca8bbb2f77cf13c155c068 by Maik Qualmann.
Committed on 29/01/2023 at 06:53.
Pushed by mqualmann into branch 'qt5-maintenance'.

ignore escape key in trash view too
FIXED-IN: 7.10.0

M  +2-1NEWS
M  +1-0core/app/views/stack/itemiconview_views.cpp

https://invent.kde.org/graphics/digikam/commit/6ab745a426ebdcc182ca8bbb2f77cf13c155c068

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 464966] Pressing Escape in Trash clears the view

2023-01-28 Thread Frank Steinmetzger
https://bugs.kde.org/show_bug.cgi?id=464966

--- Comment #1 from Frank Steinmetzger  ---
Addendum: after some more clicking around I come to the conclusion that I
actually found two separate bugs. One is that pressing Escape empties the Trash
view.

The other one is about the scrollbar:

when I open an empty album, the vertical scrollbar retains its status from the
last viewed non-empty album. Meaning:
1. I go to an album with so many images, that there would be a scrollbar grip
of—for example—50 % height (meaning: two pages worth of scrolling).
2. I go to an empty album. The scrollbar remains visible with 50 % height.
3. I go to the empty trash, all the action buttons at the bottom are disabled
(as they should, because Trash is empty and nothing is selected) and the
scrollbar disappears.
4. I go back to the empty album, the scrollbar reappears with 50 % height.
5. As soon as the view is resized, either by moving a separator or by
hiding/showing a sidebar, the scrollbar also disappears.

So when I press Escape in the Trash view which empties the view, this emptying
triggers the same behaviour as in Step 4.

-- 
You are receiving this mail because:
You are watching all bug changes.