Bug 401449 - zoom animation does not want to reset
Summary: zoom animation does not want to reset
Status: RESOLVED DUPLICATE of bug 401294
Alias: None
Product: lattedock
Classification: Plasma
Component: application (show other bugs)
Version: git (master)
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Michail Vourlakos
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-26 22:39 UTC by Ivan Bordoni
Modified: 2018-11-27 08:15 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
test1 (3.21 MB, video/mp4)
2018-11-26 22:41 UTC, Ivan Bordoni
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Bordoni 2018-11-26 22:39:40 UTC
I have not yet figured out how it triggers but I noticed that when you exit and return from the dock, the zoom animation does not reset

so to better understand, I switched from autohide mode to always visible
and I observed that there is no way to reset the zoom

then I'm back in autohide and despite the passage, the problem persists

Then, to have confirmation, again in always visible, and I observe that everything is the same as before, there is not way, to reset the zoom

then I discovered that the only way to restore normal operation was to eliminate a launcher from the dock

all this is not easy to reproduce, this evening it happened to me three times but I made several attempts and it seems quite casual and not tied to the separator

having never used the mode always visible before now, I can not confirm that depends on recent commits maybe this problem has existed for months



Operating System: openSUSE Tumbleweed 20181122
KDE Plasma Version: 5.14.80
KDE Frameworks Version: 5.52.0
Qt Version: 5.12.0
Kernel Version: 4.17.14-1-default
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-3317U CPU @ 1.70GHz
Memory: 3,6 GiB of RAM
Comment 1 Ivan Bordoni 2018-11-26 22:41:47 UTC
Created attachment 116515 [details]
test1
Comment 2 Michail Vourlakos 2018-11-27 08:15:19 UTC
*** This bug has been marked as a duplicate of bug 401294 ***