Bug 418319

Summary: Unnecessary sliding effect when I open an app under categories
Product: [Plasma] plasmashell Reporter: Patrick Silva <bugseforuns>
Component: Application Launcher (Kickoff)Assignee: David Edmundson <kde>
Status: RESOLVED DUPLICATE    
Severity: minor CC: nate, plasma-bugs
Priority: NOR    
Version: 5.18.3   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:

Description Patrick Silva 2020-02-29 10:53:20 UTC
SUMMARY
This issue affects both Arch Linux and Neon unstable.

STEPS TO REPRODUCE
1. open kickoff
2. click on "Applications" tab
3. click on any app category
4. click on any app

OBSERVED RESULT
immediately after the last step, kickoff shows a sliding effect from right to left 
and then closes

EXPECTED RESULT
kickoff should close immediately after the last step, without sliding effect.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.18.2
KDE Frameworks Version: 5.67.0
Qt Version: 5.14.1


Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.18.80
KDE Frameworks Version: 5.68.0
Qt Version: 5.14.1
Comment 1 Patrick Silva 2021-05-16 22:23:51 UTC
Pointless sliding when we click on an app perists with new kickoff.
We can set a slower animation speed in General Behavior KCM to make it
more noticeable.

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.22.80
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2
Graphics Platform: Wayland
Comment 2 Nate Graham 2021-05-17 19:07:42 UTC
I think I found the general problem. When you click on a launchable item, the favorites item also gets activated afterwards, so that it will show that view the next time yo open Kickoff. However activating the favorites item triggers another slide animation to fire. It should not.
Comment 3 Nate Graham 2021-05-17 19:20:05 UTC
This code is too convoluted for me to figure out the rest right now. Moving onto something else. Maybe someone else can fix it.
Comment 4 Nate Graham 2021-05-24 19:07:48 UTC
Marco fixed it in Bug 437558. :)

*** This bug has been marked as a duplicate of bug 437558 ***