https://bugs.kde.org/show_bug.cgi?id=429447
--- Comment #12 from Fabian Vogt <fab...@ritter-vogt.de> --- (In reply to Fabian Vogt from comment #11) > (In reply to Fabian Vogt from comment #10) > > I see that the code is using mapToGlobal quite liberally. Note that > > mapToGlobal really uses global screen coordinates, which aren't reliable and > > shouldn't be used for such calculations. > > > > I set a breakpoint at followViewContainerGeometry and it's called even > > before the window is visible, so mapToGlobal will return wrong values as > > there's no window yet. That might be the cause of this. > > > > It probably works for resizes because the window is visible at that point > > and the stored window size might just trigger a resize event with similar > > effect. > > This seems to be the case indeed. For the first few calls of adjustSpacing, > m_globalXOfSplitter is 0 here as it's just not shown yet. By updating > m_globalXOfSplitter in adjustSpacing, it's set propely on the fourth call > and the spacing calculations are correct. Should I just submit ^ as workaround? In openQA this hits in 100% of all first starts, so I expect that users will notice this. It's not that bad as just resizing the window or restarting dolphin fixes it, but it's literally the first impression... -- You are receiving this mail because: You are watching all bug changes.