https://bugs.kde.org/show_bug.cgi?id=429447
--- Comment #8 from Felix Ernst <[email protected]> --- (In reply to Fabian Vogt from comment #6) > It seems like only the first start is affected, even just > opening dolphin and immediately closing it again makes > it work on the next start. Okay, that's good. But unfortunately this also means that debugging this touches on a lot of subjects I know very little of. I'll write down what I know about this now so people more familiar with Dolphin startup, session restoration or Qt Application startup have an easy time resolving this bug report if they are able to reproduce it. - The calculation of the spacing done by DolphinNavigatorsWidgetAction::adjustSpacing() is triggered whenever a viewContainer is resized or an url is changed. Because changing the folder and therefore the url didn't fix the spacing for Fabain Vogt that means that adjustSpacing() is calculating the spacing based on wrong cached geometry of the viewContainers to begin with. - Geometry of the viewContainers is cached whenever DolphinNavigatorsWidgetAction::followViewContainerGeometry() is called. This happens only from DolphinTabPage::eventFilter() whenever a QEvent::Resize occurs for a viewContainer. This is why resizing Dolphin fixes the spacing. - This bug occuring on the first startup therefore signifies to me that there are either resize events occuring at a time at which Qt doesn't report correct geometries yet or that no resize events are occuring at all. Whenever I start Dolphin with a single tab and a single view, a total of three calls to DolphinNavigatorsWidgetAction::followViewContainerGeometry() happen, all of which leading to the correct leading spacing of 0. That's all I know for now. (In reply to Nate Graham from comment #7) > I can't reproduce this either FWIW. I was hoping your session restoration knowledge could come in handy here. :P -- You are receiving this mail because: You are watching all bug changes.
