https://bugs.kde.org/show_bug.cgi?id=430521
Elvis Angelaccio <elvis.angelac...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Latest Commit|https://invent.kde.org/fram |https://invent.kde.org/syst
|eworks/kconfig/commit/b57c7 |em/dolphin/commit/7edce5a09
|ad9acf45928a6debefcd432cc50 |c768805878d15e225cd063fb037
|432fefdb |cef3
Resolution|--- |FIXED
Version Fixed In|5.79 |21.08
--- Comment #39 from Elvis Angelaccio <elvis.angelac...@kde.org> ---
Git commit 7edce5a09c768805878d15e225cd063fb037cef3 by Elvis Angelaccio, on
behalf of Felix Ernst.
Committed on 01/08/2021 at 21:57.
Pushed by elvisangelaccio into branch 'release/21.08'.
Fix width issues when un-maximizing Dolphin
Before this commit un-maximizing or to be more precise instantly
changing the size of the window by a large amount could potentially
change the width of the sidebars, the viewContainers and the window
itself to unexpected/undesired widths.
This happened because the spacing calculation is triggered when the
primary ViewContainer is resized but at this point in time some of
the other widgets, especially the secondary ViewContainer and the
navigatorsWidget have generally not been resized yet. Therefore the
width and spacing calculations are based on partly updated and
partly outdated values leading to wrong results.
This commit makes it so calculation of spacings is delayed until
all widths have been updated.
Yes, spacing probably should not have the power to resize the
window but unfortunately the spacing can not be set to be less
forceful when taking space because otherwise the UrlNavigators
will take all space they can get with their
QSizePolicy::MinimumExpanding.
FIXED-IN: 21.08
M +12 -1 src/dolphinnavigatorswidgetaction.cpp
M +6 -0 src/dolphinnavigatorswidgetaction.h
https://invent.kde.org/system/dolphin/commit/7edce5a09c768805878d15e225cd063fb037cef3
--
You are receiving this mail because:
You are watching all bug changes.
